Skip to main content
VulnerabilityPublished

CVE-2026-87004: Quenary tugtainer · Improper Verification of Cryptographic Signature

Affects Quenary tugtainerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 1.31.3 soon.

Data as of 14 Nov 2026, 20:44 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.31.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.

What to do

Upgrade tugtainer and quenary/tugtainer to 1.31.3.

Affected software

ProductAffectedFixed in
QuenarytugtainerAffected
  • <1.31.3
Fixed in
  • 1.31.3
GitHubquenary/tugtainerpkg:github/quenary/tugtainerOther threatsAffected
  • <1.31.3
Fixed in
  • 1.31.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Tugtainer to version 1.31.3 or later, where the OIDC id_token verification correctly validates the token's signature, audience, issuer, and expiry. No other mitigation is necessary as the issue is fixed in this official release.

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.

References

Community reviews

Loading reviews…