Skip to main content
VulnerabilityPublished

CVE-2026-33494: ory oathkeeper · Relative Path Traversal

Affects ory oathkeeperSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 10.0 Critical : upgrade to 26.2.0 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.2.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade oathkeeper and ory/oathkeeper to 26.2.0.

Affected software

ProductAffectedFixed in
oryoathkeeperAffected
  • <26.2.0
Fixed in
  • 26.2.0
GitHubory/oathkeeperpkg:github/ory/oathkeeperOther threatsAffected
  • <26.2.0
Fixed in
  • 26.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

An official fix is available in ORY Oathkeeper version 26.2.0. Users should upgrade to version 26.2.0 or later to remediate this vulnerability. No additional mitigations are specified in the advisory. Patch status is confirmed by the vendor advisory indicating the fix is included in version 26.2.0.

Description

ORY Oathkeeper versions prior to 26.2.0 are affected by a critical authorization bypass vulnerability due to relative path traversal (CWE-23). The issue arises because the software uses the raw, un-normalized HTTP request path for access rule evaluation, allowing crafted URLs with path traversal sequences to bypass intended access controls. This vulnerability has a CVSS score of 10.0, indicating critical severity. Version 26.2.0 includes a patch that addresses this flaw.

References

Community reviews

Loading reviews…