CVE-2026-87004

Tugtainer: OIDC id_token claims accepted without signature/audience/expiry verification

Published Sep 30, 2026 CVSS 3.1 · 8.1 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The flaw occurs when the backend module decodes the OIDC id_token using a function that skips all cryptographic and claim validation, allowing an attacker to supply a forged token. The extracted claims are trusted as the user identity, enabling the attacker to obtain a Tugtainer session with the permissions of the targeted account. This bypasses authentication and can be used to elevate privileges within the application.

Affected Systems

The vulnerability affects the Quenary Tugtainer self‑hosted automation tool, specifically versions earlier than 1.31.3. An attacker could target any deployment of these affected releases that uses OIDC for authentication.

Risk and Exploitability

With a CVSS score of 8.1, the vulnerability is classified as high severity. Although no EPSS data is available, the lack of signature and claim validation creates a straightforward exploitation path: an attacker crafts a valid‑looking token, initiates an OIDC login, and receives a privileged session. The issue is not listed in CISA KEV, but the impact remains significant for organizations relying on the affected application.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Quenary Tugtainer v1.31.3 or later, which includes the signature and audience validation fix.
  • If upgrading is not immediately possible, disable or remove OIDC authentication until the patch is applied to prevent unauthenticated access.
  • Verify the identity provider configuration so that only properly signed tokens are accepted and that audience, issuer and expiry checks are enforced.

Generated by OpenCVE AI on September 30, 2026 at 20:03 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Quenary
Quenary tugtainer
Vendors & Products Quenary
Quenary tugtainer
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Tugtainer: OIDC id_token claims accepted without signature/audience/expiry verification
Weaknesses CWE-347
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 30, 2026, 6:01 PM
Reserved
Sep 8, 2026, 4:44 PM
Status
Deferred
Published
Sep 30, 2026, 6:18 PM
Modified
Sep 30, 2026, 7:57 PM