CVE-2026-87004Public exploitNetwork attack vectorHinoki check available

OIDC impersonation via unverified ID token claims

Published Sep 30, 2026 · Updated Sep 30, 2026

Authentication bypass in Quenary Tugtainer before 1.31.3 allows remote attackers to impersonate users through forged OIDC ID tokens. During OIDC login, auth_oidc_provider.py calls jwt.get_unverified_claims() on the provider token and uses its identity claims as the session user without validating the signature, audience, issuer, or expiry. Exploitation requires an on-path position or control of the configured identity provider or token endpoint; a forged token then yields a session for the chosen identity.

CVSS severity8.1
High
EPSS probability0.34%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Authentication bypass in Quenary Tugtainer before 1.31.3 allows remote attackers to impersonate users through forged OIDC ID tokens. During OIDC login, auth_oidc_provider.py calls jwt.get_unverified_claims() on the provider token and uses its identity claims as the session user without validating the signature, audience, issuer, or expiry. Exploitation requires an on-path position or control of the configured identity provider or token endpoint; a forged token then yields a session for the chosen identity.

The record

CVE
CVE-2026-87004
Published
Sep 30, 2026
Updated
Sep 30, 2026
Vendor
Quenary
Product
Tugtainer
Classifications
CWE-347, T1606
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 30, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 30, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.31.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Quenary · Tugtainerversion=< 1.31.3

Published CVSS scores

8.1QuenaryCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature
T1606Forge Web Credentials

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started