Quick answers
- Is CVE-2026-87004 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87004 being exploited in the wild.
- How severe is CVE-2026-87004?
- High severity, with a CVSS score of 8.1, published 30 September 2026.
- Which products and versions are affected?
- Quenary Tugtainer prior to 1.31.3.
- Is there a fix for CVE-2026-87004?
- A patch was published on 2026-08-06. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-87004 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-87004?
- Check whether you run Quenary Tugtainer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The auth_oidc_provider.py module used jose.jwt.get_unverified_claims() instead of jwt.decode() to process ID tokens from the OIDC token endpoint, bypassing signature verification, audience (aud) validation, issuer (iss) validation, and expiry (exp) checking. An attacker with network access to an identity provider or capable of intercepting the OIDC flow could forge an ID token with arbitrary email/sub/preferred_username claims to create or hijack user sessions. The vulnerability is network-accessible and requires no authentication or user interaction to exploit.
Affected products
- Quenary Tugtainer prior to 1.31.3
Timeline
- 2026-09-30: disclosed
- 2026-08-06: patched