Cross-tenant access via shared introspection cache
Published Sep 8, 2026 · Updated Sep 10, 2026
Authentication bypass in IBM Enterprise Build of Quarkus 3.27.1 through 3.27.5 and 3.33.1 through 3.33.3 allows remote attackers cross-tenant access. The OIDC component keys shared token-introspection cache entries by token without binding the cached result to the tenant that validated it. Exploitation requires multiple OIDC tenants, enabled introspection caching, and a valid token for one tenant; protected resources assigned to another tenant can then be read.
Summary
What happened
Authentication bypass in IBM Enterprise Build of Quarkus 3.27.1 through 3.27.5 and 3.33.1 through 3.33.3 allows remote attackers cross-tenant access. The OIDC component keys shared token-introspection cache entries by token without binding the cached result to the tenant that validated it. Exploitation requires multiple OIDC tenants, enabled introspection caching, and a valid token for one tenant; protected resources assigned to another tenant can then be read.
The record
- CVE
- CVE-2026-19625
- Published
- Sep 8, 2026
- Updated
- Sep 10, 2026
- Vendor
- IBM
- Product
- IBM Enterprise Build of Quarkus
- Classifications
- CWE-524, CWE-284, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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.
- Affected versionversion=3.27.1 <=3.27.5
- Affected versionversion=3.33.1 <=3.33.3
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo