Vulnerabilities in pkg:golang/github.com/ory/oathkeeper

PACKAGE
Advisory Identifier: GHSA-p224-6x5r-fjpm
Advisory Summary

CVE-2026-33494 is a CRITICAL (CVSS 10.0) path traversal vulnerability (CWE-23: Relative Path Traversal) affecting Github.com/ory/oathkeeper libraries in the Go ecosystem. The issue involves ory oathkeeper has a path traversal authorization bypass. Remediation is available by upgrading affected packages to version 0.40.10-0.20260320084758-8e0002140491.

6 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/ory/oathkeeper

6 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/ory/oathkeeper. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-p224-6x5r-fjpm CVE-2026-33494 CRITICAL Ory Oathkeeper has a path traversal authorization bypass
GHSA-4mq7-pvjg-xp2r CVE-2026-33496 HIGH Ory Oathkeeper has an authentication bypass by cache key confusion
GHSA-vhr5-ggp3-qq85 CVE-2026-33495 MODERATE Ory Oathkeeper has an authentication bypass by usage of untrusted header
GHSA-w9mr-28mw-j8hg - LOW Hop-by-hop abuse to malform header mutator
GHSA-vfvf-6gx5-mqv6 CVE-2021-32701 HIGH Incorrect Authorization in ORY Oathkeeper
GHSA-qvp4-rpmr-xwrr - HIGH Possible bypass of token claim validation when OAuth2 Introspection caching is enabled

CVE-2026-33494 at a Glance

CVE Identifier CVE-2026-33494
GHSA Identifier GHSA-p224-6x5r-fjpm
Severity CRITICAL
CVSS v3.1 Base Score 10.0
CWE Classification CWE-23: Relative Path Traversal
Affected Product Github.com/ory/oathkeeper
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 10.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-33494

To remediate this vulnerability, upgrade all affected Github.com/ory/oathkeeper dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/ory/oathkeeper fixed: 0.40.10-0.20260320084758-8e0002140491
Upgrade github.com/ory/oathkeeper to 0.40.10-0.20260320084758-8e0002140491
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/ory/oathkeeper

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-33494, inspect your project dependencies for Github.com/ory/oathkeeper:

inspect dependencies for github.com/ory/oathkeeper

Analyze the terminal output to locate any version of Github.com/ory/oathkeeper in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.40.10-0.20260320084758-8e0002140491), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-23: Relative Path Traversal, where the product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory. In Github.com/ory/oathkeeper, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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 <a href="https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#envoy-v3-api-field-extensions-filters-network-http-connection-manager-v3-httpconnectionmanager-normalize-path" target="_blank" rel="noopener noreferrer">Envoy docs on path normalization</a>. ### Cloudflare Cloudflare normalizes URLs by default. In the Cloudflare dashboard, ensure **Normalize incoming URLs** is enabled under **Rules → Normalization**. See the <a href="https://developers.cloudflare.com/rules/normalization/" target="_blank" rel="noopener noreferrer">Cloudflare URL normalization docs</a>.

CVE-2026-33494 Affected Github.com/ory/oathkeeper Versions

1 component(s)
Fixed Versions:
0.40.10-0.20260320084758-8e0002140491
Product / Package Ecosystem Affected Versions Fixed Version
github.com/ory/oathkeeper
Go
< 0.40.10-0.20260320084758-8e0002140491
0.40.10-0.20260320084758-8e0002140491

References

Frequently Asked Questions

What is CVE-2026-33494?
CVE-2026-33494 is a security vulnerability in Github.com/ory/oathkeeper involving Ory Oathkeeper has a path traversal authorization bypass under CWE-23: Relative Path Traversal.
Which Github.com/ory/oathkeeper versions are affected?
Affected versions include releases prior to 0.40.10-0.20260320084758-8e0002140491 across affected packages: github.com/ory/oathkeeper.
What version fixes CVE-2026-33494?
Upgrading to 0.40.10-0.20260320084758-8e0002140491 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/ory/oathkeeper affected?
Yes, github.com/ory/oathkeeper is affected in releases prior to 0.40.10-0.20260320084758-8e0002140491. Upgrade your dependency to 0.40.10-0.20260320084758-8e0002140491 or later.
What is the CVSS score of CVE-2026-33494?
CVE-2026-33494 has a CVSS v3.1 base score of 10.0 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N.
What CWE is associated with CVE-2026-33494?
CVE-2026-33494 is classified under CWE-23: Relative Path Traversal (The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory.).
How can I check Go dependencies for CVE-2026-33494?
Run the dependency tree command: 'inspect dependencies for github.com/ory/oathkeeper'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p224-6x5r-fjpm",
  "modified" : "2026-03-27T20:59:22Z",
  "published" : "2026-03-20T20:51:24Z",
  "aliases" : [ "CVE-2026-33494" ],
  "summary" : "Ory Oathkeeper has a path traversal authorization bypass",
  "details" : "## Description\n\nOry 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.\n\n## Preconditions\n\nOry Oathkeeper rules are typically configured with patterns like:\n\n```\n/public/<.*>   → allow unauthenticated access\n/admin/<.*>    → require authentication\n```\n\nWithout 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.\n\n## Mitigation\n\nGoing 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.\n\nAs 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.\n\n## Defense in depth: Cleaning paths before Oathkeeper\n\nEven 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.\n\n### Nginx\n\nNginx normalizes paths by default when using `proxy_pass`. Alternatively, use `$uri` (which Nginx normalizes) rather than `$request_uri` in your matching rules.\n\n### Envoy\n\nEnable the `normalize_path` option (available since Envoy 1.14) to normalize the path components before matching and forwarding. See the <a href=\"https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#envoy-v3-api-field-extensions-filters-network-http-connection-manager-v3-httpconnectionmanager-normalize-path\" target=\"_blank\" rel=\"noopener noreferrer\">Envoy docs on path normalization</a>.\n\n### Cloudflare\n\nCloudflare normalizes URLs by default. In the Cloudflare dashboard, ensure **Normalize incoming URLs** is enabled under **Rules → Normalization**.\nSee the <a href=\"https://developers.cloudflare.com/rules/normalization/\" target=\"_blank\" rel=\"noopener noreferrer\">Cloudflare URL normalization docs</a>.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/ory/oathkeeper"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.40.10-0.20260320084758-8e0002140491"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/ory/oathkeeper/security/advisories/GHSA-p224-6x5r-fjpm"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33494"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ory/oathkeeper/commit/8e0002140491c592db41fa141dc6ad68f417e2b2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ory/oathkeeper"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-23" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-20T20:51:24Z",
    "nvd_published_at" : "2026-03-26T18:16:30Z"
  }
}