Skip to main content
← Go

github.com/ory/oathkeeper

4 known vulnerabilities (1 critical, 2 high, 1 medium), with the versions each affects and the releases that fix them.

Latest release
v0.40.9 (Jan 30, 2025): affected by 3 advisories
Newest unaffected release
Every release is affected by at least one advisory
Advisories
4 · 1 critical, 2 high, 1 medium
Releases
121 since v0.0.1 (Oct 10, 2017)
Registry
pkg.go.dev
Releases read
Nov 8, 2026

Version timeline

  • CVE-2026-33496
    Affects v0.0.1 to v0.40.9 (v1.0.0-beta.1 is outside it)
  • CVE-2026-33495
    Affects v0.0.1 to v0.40.9 (v1.0.0-beta.1 is outside it)
  • CVE-2026-33494
    Affects v0.0.1 to v0.40.9 (v1.0.0-beta.1 is outside it)
  • CVE-2021-32701
    Affects v0.38.0-beta.2 to v0.38.11-beta.1 (v0.38.12-beta.1 is outside it)
Every release cve.now has on record, lowest version on the left; each bar is a run of versions an advisory affects.

Advisories 4

  • Ory Oathkeeper has an authentication bypass by cache key confusion

    Affected: fixed in 0.40.10-0.20260320084801-198a2bc82a99.

    No fix released. The advisory names 0.40.10-0.20260320084801-198a2bc82a99 as the fix, which the registry doesn't have yet. The latest release, v0.40.9, is still affected.

  • CVE-2026-33495Medium 6.5

    Ory Oathkeeper has an authentication bypass by usage of untrusted header

    Affected: fixed in 0.40.10-0.20260320084810-e9acca14a04d.

    No fix released. The advisory names 0.40.10-0.20260320084810-e9acca14a04d as the fix, which the registry doesn't have yet. The latest release, v0.40.9, is still affected.

  • CVE-2026-33494Critical 10.0

    Ory Oathkeeper has a path traversal authorization bypass

    Affected: fixed in 0.40.10-0.20260320084758-8e0002140491.

    No fix released. The advisory names 0.40.10-0.20260320084758-8e0002140491 as the fix, which the registry doesn't have yet. The latest release, v0.40.9, is still affected.

  • Possible bypass of token claim validation when OAuth2 Introspection caching is enabled

    Affected: from 0.38.0-beta.2, fixed in 0.38.12-beta.1.

    Fixed in v0.38.12-beta.1 (released Jun 22, 2021, the day of disclosure).

    The latest release, v0.40.9, is not affected.