CVE-2026-33494 affects ORY Oathkeeper, an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests using configured Access Rules. In versions prior to 26.2.0, Oathkeeper evaluates authorization rules against the raw, un-normalized HTTP request path. An attacker can supply a crafted path containing traversal sequences such as /public/../admin/secrets; although that path normalizes to a protected resource, the raw path may still match a permissive rule intended for a public location. This discrepancy between rule evaluation and normalized path resolution enables an authorization bypass to protected endpoints.
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.
Patch, then assume compromise.
8e0002140491c592db41fa141dc6ad68f417e2b2 and public advisory GHSA-p224-6x5r-fjpm.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.
9 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.