LowGO-2022-0406GHSA-qvp4-rpmr-xwrr

Possible bypass of token claim validation when OAuth2 Introspection caching is enabled in github.com/ory/oathkeeper

Published 21 Aug 2024 · Updated 13 Mar 2026

Is your project on an affected github.com/ory/oathkeeper?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=0.38.0-beta.2 <0.38.12-beta.1
Fixed in
0.38.12-beta.1
Update to the fixed version for your release line, for example:go get github.com/ory/oathkeeper@v0.38.12-beta.1

Details

Possible bypass of token claim validation when OAuth2 Introspection caching is enabled in github.com/ory/oathkeeper

Is GO-2022-0406 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/ory/oathkeeper, and gives you the command that fixes it.

More advisories for github.com/ory/oathkeeper

  • LowCVE-2026-33494Ory Oathkeeper has a path traversal authorization bypass in github.com/ory/oathkeeper · 23 Mar 2026
  • LowCVE-2026-33495Ory Oathkeeper has an authentication bypass by usage of untrusted header in github.com/ory/oathkeeper · 23 Mar 2026
  • LowCVE-2026-33496Ory Oathkeeper has an authentication bypass by cache key confusion in github.com/ory/oathkeeper · 23 Mar 2026
  • CriticalCVE-2026-33494Ory Oathkeeper has a path traversal authorization bypass · 20 Mar 2026
  • HighCVE-2026-33496Ory Oathkeeper has an authentication bypass by cache key confusion · 20 Mar 2026
  • MediumCVE-2026-33495Ory Oathkeeper has an authentication bypass by usage of untrusted header · 20 Mar 2026
All 10 advisories for github.com/ory/oathkeeper

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.