Advisory record · GHSA-p224-6x5r-fjpm

Ory Oathkeeper has a path traversal authorization bypass

CVSS 10.0 CriticalCriticalEPSS 0.0054 · 46th percentile

Critical, because:

  • CVSS score 10.0: 9.0 or more.

How we decide what’s critical

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.

PackageEcosystemAffectedFixed in
github.com/ory/oathkeeperGo<0.40.10-0.20260320084758-8e00021404910.40.10-0.20260320084758-8e0002140491
Identifiers
GHSA-p224-6x5r-fjpm · CVE-2026-33494 · GO-2026-4804
Weakness (CWE)
CWE-23
Published
20 Mar 2026
Updated
27 Mar 2026

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

ScoreRatingCVSSVectorSource
10.0 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N 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

  1. 31 Oct 2026, 15:08 UTC First seen by agentprime
  2. 31 Oct 2026, 15:08 UTC Confirmed by OSV

Sources

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.