Loading vulnerability…
CVE-2026-33496 affects ORY Oathkeeper versions prior to 26.2.0. The vulnerability is an authentication bypass caused by cache key confusion in the oauth2_introspection authenticator. Cached token introspection results are keyed without distinguishing the introspection server URL, so the same token value can be treated as valid across access rules that rely on different introspection endpoints. In deployments with multiple oauth2_introspection authenticators backed by different introspection servers that accept different tokens, an attacker can first present a legitimately valid token to prime the cache for one server and then reuse that token against a rule using a different introspection server, resulting in incorrect authorization decisions.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
oauth2_introspection authenticators. This removes the cache key confusion condition and prevents token validation results from being incorrectly shared between different introspection servers.Patch, then assume compromise.
oauth2_introspection cache key, preventing cached validation results from being reused across different introspection backends. A referenced fix was published in commit 198a2bc82a99e0a77bd0ffe290cbdd5285a1b17c.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.