Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-33495— Ory Oathkeeper has an authentication bypass by usage of untrusted header

Quick assessment

Affected
ory oathkeeper
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Ory Oathkeeper是Ory开源的一个访问控制决策软件。 ORY Oathkeeper 26.2.0之前版本存在安全漏洞，该漏洞源于未正确遵循配置，始终信任X-Forwarded-Proto标头，可能导致规则匹配绕过。

CVSS 6.5 · Medium EPSS 0.28% · P18
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-33495

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Ory Oathkeeper has an authentication bypass by usage of untrusted header
Source: CVE Program / CVE List V5
Vulnerability Description
ORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. Ory Oathkeeper is often deployed behind other components like CDNs, WAFs, or reverse proxies. Depending on the setup, another component might forward the request to the Oathkeeper proxy with a different protocol (http vs. https) than the original request. In order to properly match the request against the configured rules, Oathkeeper considers the `X-Forwarded-Proto` header when evaluating rules. The configuration option `serve.proxy.trust_forwarded_headers` (defaults to false) governs whether this and other `X-Forwarded-*` headers should be trusted. Prior to version 26.2.0, Oathkeeper did not properly respect this configuration, and would always consider the `X-Forwarded-Proto` header. In order for an attacker to abuse this, an installation of Ory Oathkeeper needs to have distinct rules for HTTP and HTTPS requests. Also, the attacker needs to be able to trigger one but not the other rule. In this scenario, the attacker can send the same request but with the `X-Forwarded-Proto` header in order to trigger the other rule. We do not expect many configurations to meet these preconditions. Version 26.2.0 contains a patch. Ory Oathkeeper will correctly respect the `serve.proxy.trust_forwarded_headers` configuration going forward, thereby eliminating the attack scenario. We recommend upgrading to a fixed version even if the preconditions are not met. As an additional mitigation, it is generally recommended to drop any unexpected headers as early as possible when a request is handled, e.g. in the WAF.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制缺失
Source: CVE Program / CVE List V5
Vulnerability Title
Ory Oathkeeper 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Ory Oathkeeper是Ory开源的一个访问控制决策软件。 ORY Oathkeeper 26.2.0之前版本存在安全漏洞，该漏洞源于未正确遵循配置，始终信任X-Forwarded-Proto标头，可能导致规则匹配绕过。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
ory oathkeeper < 26.2.0 -

II. Public POCs for CVE-2026-33495

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-33495

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-33495 (1)

Vendor Advisories for CVE-2026-33495 (1)

Same Patch Batch · ory · 2026-03-26 · 7 CVEs total

CVE-2026-33494 10.0 CRITICAL Ory Oathkeeper has a path traversal authorization bypass
CVE-2026-33506 8.8 HIGH DOM-Based XSS in Ory Polis Login Page
CVE-2026-33496 8.1 HIGH Ory Oathkeeper has an authentication bypass by cache key confusion
CVE-2026-33503 7.2 HIGH Ory Kratos has a SQL injection via forged pagination tokens
CVE-2026-33504 7.2 HIGH Ory Hydra has a SQL injection via forged pagination tokens
CVE-2026-33505 7.2 HIGH Ory Keto has a SQL injection via forged pagination tokens

IV. Related Vulnerabilities

Same product: oathkeeper
Same vendor: ory
Same weakness: CWE-862

V. Comments for CVE-2026-33495

No comments yet

Leave a comment