CVE-2026-33494
ORY · Oathkeeper
ORY Oathkeeper versions prior to 26.2.0 are vulnerable to an authorization bypass via HTTP path traversal where raw paths are matched against permissive rules before normalization.
Executive summary
ORY Oathkeeper is subject to a critical authorization bypass that allows unauthenticated attackers to access protected administrative endpoints by utilizing path traversal sequences in HTTP requests.
Vulnerability
The vulnerability exists in the rule evaluation engine, which uses un-normalized HTTP paths to match access rules. An unauthenticated attacker can craft a URL containing traversal sequences (e.g., /public/../admin) that bypasses restrictive rules but resolves to protected paths after server-side normalization.
Business impact
This flaw effectively nullifies the security posture of the Identity & Access Proxy, allowing unauthorized access to sensitive internal APIs and administrative secrets. Given the CVSS score of 10.0, the risk is maximum, as it enables complete bypass of the primary security gatekeeper for protected infrastructure.
Remediation
Immediate Action: Upgrade ORY Oathkeeper to version 26.2.0 or later immediately to ensure that path normalization occurs prior to access rule evaluation.
Proactive Monitoring: Review access logs for requests containing dot-dot-slash (../) sequences targeted at known public or permissive endpoints.
Compensating Controls: Ensure that downstream services perform their own secondary authorization checks and utilize a WAF to block requests containing URL-encoded path traversal characters.
Exploitation status
Public Exploit Available: false
Analyst recommendation
As an Identity and Access Proxy, the failure of Oathkeeper to correctly normalize paths is a fundamental security failure. Organizations must prioritize this update to prevent unauthorized actors from reaching internal resources that rely on the proxy for protection.