Quenary Tugtainer
Tugtainer: OIDC id_token claims accepted without signature/audience/expiry verification
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.31.3
Fixed in 1.31.3
Mitigation
Upgrade tugtainer to 1.31.3 or later.
References
- Vendor advisory github.com/Quenary/tugtainer/security/advisori…
- Patch github.com/Quenary/tugtainer/commit/b55269b6a3…
- Release notes github.com/Quenary/tugtainer/releases/tag/v1.3…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 informational
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| squeeze440/tugtainer-PoC | 3 Sep 2026 −27 d | 0 | Informational · detection |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.