GHSA-p224-6x5r-fjpm

Source

https://github.com/advisories/GHSA-p224-6x5r-fjpm

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/03/GHSA-p224-6x5r-fjpm/GHSA-p224-6x5r-fjpm.json

JSON Data

https://api.test.osv.dev/v1/vulns/GHSA-p224-6x5r-fjpm

Aliases

Published

2026-03-20T20:51:24Z

Modified

2026-03-27T21:20:48Z

Severity

10.0 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N CVSS Calculator

Summary

Ory Oathkeeper has a path traversal authorization bypass

Details

Description

Ory Oathkeeper is vulnerable to an authorization bypass via HTTP path traversal. An attacker can craft a URL containing path traversal sequences (e.g. /public/../admin/secrets) that resolves to a protected path after normalization, but is matched against a permissive rule because the raw, un-normalized path is used during rule evaluation.

Preconditions

Ory Oathkeeper rules are typically configured with patterns like:

/public/<.*>   → allow unauthenticated access
/admin/<.*>    → require authentication

Without path normalization, a request to /public/../admin/secrets is matched against the raw path /public/../admin/secrets. This matches the /public/<.*> rule, bypassing the authentication required for /admin/secrets. After Ory Oathkeeper permits the request, the upstream server normalizes the path and serves the protected /admin/secrets resource.

Mitigation

Going forward, Ory Oathkeeper normalizes the request path before performing rule matching and before forwarding. The path /public/../admin/secrets is normalized to /admin/secrets, which correctly matches the /admin/<.*> rule and triggers authentication.

As an immediate mitigation, all requests reaching Oathkeeper should be normalized, as described in the section below. Oathkeeper should be upgraded to a fixed version as soon as possible.

Defense in depth: Cleaning paths before Oathkeeper

Even after this fix, it is good practice to normalize HTTP paths in the layers in front of Oathkeeper. This provides defense in depth and protects against similar bypasses in other components. The following examples show how to achieve this with common reverse proxies and CDNs.

Nginx

Nginx normalizes paths by default when using proxy_pass. Alternatively, use $uri (which Nginx normalizes) rather than $request_uri in your matching rules.

Envoy

Enable the normalize_path option (available since Envoy 1.14) to normalize the path components before matching and forwarding. See the Envoy docs on path normalization.

Cloudflare

Cloudflare normalizes URLs by default. In the Cloudflare dashboard, ensure Normalize incoming URLs is enabled under Rules → Normalization. See the Cloudflare URL normalization docs.

Database specific

{
    "cwe_ids": [
        "CWE-23"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-20T20:51:24Z",
    "nvd_published_at": "2026-03-26T18:16:30Z",
    "severity": "CRITICAL"
}

References

Affected packages

Go / github.com/ory/oathkeeper

Package

Name: github.com/ory/oathkeeper; View open source insights on deps.dev
Purl: pkg:golang/github.com/ory/oathkeeper

Affected ranges

Type: SEMVER
Events: Introduced

0 Unknown introduced version / All previous versions are affected

Fixed

0.40.10-0.20260320084758-8e0002140491

Database specific

source

"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/03/GHSA-p224-6x5r-fjpm/GHSA-p224-6x5r-fjpm.json"