CVE-2026-87004Tugtainer: OIDC id_token claims accepted without signature/audience/expiry verification
Updated under an hour ago ()
Does this affect you?
It affects Quenary tugtainer. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.34%, higher than 25% of scored CVEs.
Do this next
Free account, 1 product
Tugtainer is a self-hosted app for automating updates of Docker containers. Prior to version 1.31.3, when the OIDC login flow completes, backend/modules/auth/providers/auth_oidc_provider.py decodes the id_token returned by the identity provider's token endpoint using jose.jwt.get_unverified_claims() instead of jwt.decode(). This skips signature verification, audience (aud) validation, issuer (iss) validation, and expiry (exp) checking entirely. The extracted claims (email/sub/preferred_username) are then used directly as the user_id for the resulting Tugtainer session. This issue has been patched in version 1.31.3.
- CVSS
- 8.1 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- CWE-347
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.34% (percentile 25)
- Assigned by
- GitHub_M
- NVD analysis
- Deferred
- Record last updated
- Sep 30, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Quenary tugtainer quenary:tugtainer (from the name) | before 1.31.3 | CNA record |
References
- https://github.com/Quenary/tugtainer/security/advisories/GHSA-crjc-6vc7-xrfhx-refsource-confirm
- https://github.com/Quenary/tugtainer/commit/b55269b6a3bfd43b0f2f5bd5f137ee0c81b7c2e4x-refsource-misc
- https://github.com/Quenary/tugtainer/releases/tag/v1.31.3x-refsource-misc
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.