CVE-2026-33496: GO-2026-4799 - Ory Oathkeeper has an authentication bypass by cache key confusion in github.com/ory/oathkeeper

CVE-2026-33496 · Severity: low · CVSS 3.1 · Published 2026-03-23

Ory Oathkeeper has an authentication bypass by cache key confusion in github.com/ory/oathkeeper

Technologies: github.com/ory/oathkeeper (Go). Vendors: Go.

Quick answers

Is CVE-2026-33496 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-33496 being exploited in the wild.
How severe is CVE-2026-33496?
Low severity, with a CVSS score of 3.1, published 23 March 2026.
Which products and versions are affected?
github.com/ory/oathkeeper (Go) SEMVER:introduced=0,fixed=0.40.10-0.20260320084801-198a2bc82a99.
Is there a fix for CVE-2026-33496?
Yes. github.com/ory/oathkeeper (Go): upgrade to 0.40.10-0.20260320084801-198a2bc82a99 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-33496?
Check whether you run github.com/ory/oathkeeper (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/ory/oathkeeper (Go): upgrade to 0.40.10-0.20260320084801-198a2bc82a99 or later
    go get github.com/ory/oathkeeper@v0.40.10-0.20260320084801-198a2bc82a99

Affected products

  • github.com/ory/oathkeeper (Go) SEMVER:introduced=0,fixed=0.40.10-0.20260320084801-198a2bc82a99

Identifiers

  • CVE-2026-33496
  • GHSA-4mq7-pvjg-xp2r
  • GO-2026-4799

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.