# Ory Oathkeeper has a path traversal authorization bypass

Advisory record · `GHSA-p224-6x5r-fjpm`

- **Identifiers:** `GHSA-p224-6x5r-fjpm` · `CVE-2026-33494` · `GO-2026-4804`
- **State:** Confirmed
- **Severity:** CVSS 10.0 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-23](https://cwe.mitre.org/data/definitions/23.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 20 Mar 2026
- **Updated:** 27 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Mar 2026, 20:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 10.0: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/ory/oathkeeper` (Go): affected `<0.40.10-0.20260320084758-8e0002140491`; fixed in `0.40.10-0.20260320084758-8e0002140491`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Ory Oathkeeper versions before 0.40.10-0.20260320084758-8e0002140491 are vulnerable to an authorization bypass via path traversal sequences in the request URL. Because rules match the raw, un-normalized path, a request such as one containing "/public/../" in front of a protected path can be permitted by a permissive rule while the upstream server serves the protected resource. Upgrade to 0.40.10-0.20260320084758-8e0002140491 or later. The source also recommends normalizing request paths in front of Oathkeeper, such as at a reverse proxy or CDN.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 10.0 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0054, the 46th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:08 UTC: First seen by agentprime
- 31 Oct 2026, 15:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-p224-6x5r-fjpm)

## Sources

- [GitHub Advisory Database: GHSA-p224-6x5r-fjpm](https://github.com/advisories/GHSA-p224-6x5r-fjpm)
- [OSV: GHSA-p224-6x5r-fjpm](https://osv.dev/vulnerability/GHSA-p224-6x5r-fjpm)
- <https://github.com/ory/oathkeeper/security/advisories/GHSA-p224-6x5r-fjpm>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-33494>
- <https://github.com/ory/oathkeeper/commit/8e0002140491c592db41fa141dc6ad68f417e2b2>
- <https://github.com/ory/oathkeeper>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-p224-6x5r-fjpm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-p224-6x5r-fjpm/>. Everything for agents: <https://agentprime.io/llms.txt>.
