VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/ory/oathkeeper: vulnerability history, versions and safety

github.com/ory/oathkeeper is a package in the Go ecosystem. Vulert records 12 vulnerabilities for it across 120 releases, from Jun 2021 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
12 vulnerabilities recorded C1 H3 M1 L1 U6
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
6 in the last 12 months

Most recent disclosure 23 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/ory/oathkeeper vulnerabilities

Vulert verdict on github.com/ory/oathkeeper v0.40.9 i

Updated on 22 Oct 2026

Action needed: v0.40.9 has 8 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 65/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v0.40.9 — affected i
  • Vulnerabilities on record 12 over 4 years · 6 in the last year i
  • Latest disclosure 23 Mar 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Stars 3,608 i
  • OpenSSF scorecard 5/10 i
  • Last release 20 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/ory/oathkeeper, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20260727152358-ab46001dc7d7 27 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260727152358-ab46001dc7d7 27 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260727083826-34bac3b09203 27 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260727083826-34bac3b09203 27 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260724170530-024fbb5f2b27 24 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260724170530-024fbb5f2b27 24 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260722154609-37a3bcf1752a 22 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260722154609-37a3bcf1752a 22 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260721132236-c70d37e1d38e 21 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260716092957-c00176149e42 16 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260716092957-c00176149e42 16 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260713142003-fad2dc27f20a 13 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260713142003-fad2dc27f20a 13 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260710074948-9b97eaed8fbc 10 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260710074948-9b97eaed8fbc 10 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260708122233-b3d9174de67c 08 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260708122233-b3d9174de67c 08 Jul 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260625142600-150e16fa0525 25 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260625142600-150e16fa0525 25 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260623182104-53d44091e41e 23 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260623182104-53d44091e41e 23 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260622221805-6dfb8b6e759e 22 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260622221805-6dfb8b6e759e 22 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260616154406-2b618d921aea 16 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260616154406-2b618d921aea 16 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260612104659-c0d6cdc673dd 12 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260612104659-c0d6cdc673dd 12 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260611170542-4eb4d13cfd39 11 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260611170542-4eb4d13cfd39 11 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260611110134-5b4beb224b9c 11 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260611110134-5b4beb224b9c 11 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260610103414-ba10ec0bc6ab 10 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260610103414-ba10ec0bc6ab 10 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260605122009-80ed3e3b1323 05 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260605122009-80ed3e3b1323 05 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260604200033-68db7e086200 04 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260604200033-68db7e086200 04 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260601134135-d55f9f7675b6 01 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260601134135-d55f9f7675b6 01 Jun 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260529091508-046df4d7d586 29 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260529091508-046df4d7d586 29 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260528133806-48d1baf98bd8 28 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260528133806-48d1baf98bd8 28 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260521130459-1a9cb5f27173 21 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260521130459-1a9cb5f27173 21 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260521082816-2867c7eae814 21 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260521082816-2867c7eae814 21 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260515100613-18212fcfa9d8 15 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260515100613-18212fcfa9d8 15 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260507183346-00fa2abc64c3 07 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260507183346-00fa2abc64c3 07 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260506140847-f73d68204ef8 06 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260506140847-f73d68204ef8 06 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260505174607-1f958843419a 05 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260505174607-1f958843419a 05 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260504095421-7b3a8e286fcf 04 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260504095421-7b3a8e286fcf 04 May 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260428124302-7b2002cbfbb7 28 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260428124302-7b2002cbfbb7 28 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260427111646-c0211fc34ad2 27 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260427111646-c0211fc34ad2 27 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260422132919-3f43600ec5c2 22 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260417134416-d6a0ba504aec 17 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260417134416-d6a0ba504aec 17 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260414113848-eb81e90f8bcf 14 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260414113848-eb81e90f8bcf 14 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260402091001-7f3bd8974e47 02 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260402091001-7f3bd8974e47 02 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260401131506-e533163e0b37 01 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260401131506-e533163e0b37 01 Apr 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260327085237-66852121603f 27 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260327085237-66852121603f 27 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260325083009-f0e534285c97 25 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260325083009-f0e534285c97 25 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260323154036-78b10c872c6e 23 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260320114014-bc7057b07aea 20 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260320114014-bc7057b07aea 20 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260320110134-c84dbe07ecbf 20 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260320084810-e9acca14a04d 20 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260320084806-aee85c319bc7 20 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260320084801-198a2bc82a99 20 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260320084758-8e0002140491 20 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260309111831-3f4085a207e7 09 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260309111831-3f4085a207e7 09 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260305230846-addb79fc3779 05 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260305230846-addb79fc3779 05 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260304134240-bff5f54cc744 04 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260304134240-bff5f54cc744 04 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260302085434-cb65b0709b3f 02 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260302085434-cb65b0709b3f 02 Mar 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260227150537-96679830dfce 27 Feb 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260227150537-96679830dfce 27 Feb 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260219185740-e690c00c3746 19 Feb 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260219185740-e690c00c3746 19 Feb 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260218095400-bf852603e503 18 Feb 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260218095400-bf852603e503 18 Feb 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260213084456-2b33f5a2bd50 13 Feb 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260213084456-2b33f5a2bd50 13 Feb 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260210151232-1322ee302721 10 Feb 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.40.10-0.20260210151232-1322ee302721 10 Feb 2026 C1 H1 M1 L1 U4 Apache-2.0 Yes Details →
v0.0.0-20260204162011-0b855e44c4b7 04 Feb 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.40.10-0.20260204162011-0b855e44c4b7 04 Feb 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.0.0-20260130074435-f234fba1e934 30 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.40.10-0.20260130074435-f234fba1e934 30 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.0.0-20260128214135-c019a1335435 28 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.40.10-0.20260128214135-c019a1335435 28 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.0.0-20260122154620-82e6cfb5dfd1 22 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.40.10-0.20260122154620-82e6cfb5dfd1 22 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.0.0-20260116085949-2a11ffc2dbdb 16 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.40.10-0.20260116085949-2a11ffc2dbdb 16 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.40.10-0.20260115091729-9163541edb50 15 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.0.0-20260113090244-d5931bcf08f5 13 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.40.10-0.20260113090244-d5931bcf08f5 13 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.0.0-20260109085115-d9f227a3817e 09 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.40.10-0.20260109085115-d9f227a3817e 09 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.0.0-20260102115901-9ef6345d691b 02 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.40.10-0.20260102115901-9ef6345d691b 02 Jan 2026 C1 H1 M1 L1 U4 — Yes Details →
v0.0.0-20251229085804-b32cc90b3a00 29 Dec 2025 C1 H1 M1 L1 U4 — Yes Details →
v0.40.10-0.20251229085804-b32cc90b3a00 29 Dec 2025 C1 H1 M1 L1 U4 — Yes Details →
v0.0.0-20251223144725-5c91d9d6ed45 23 Dec 2025 C1 H1 M1 L1 U4 — Yes Details →

The newest 120 of 1,448 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2023 1
  • 2024 3
  • 2026 6

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 6 of the 12 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/ory/oathkeeper

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-33494: Ory Oathkeeper Path Traversal Authorization Bypass Vulnerability 10.0 critical 0.40.10-0.20260320084758-8e0002140491 20 Mar 2026
CVE-2026-33496: Ory Oathkeeper Authentication Bypass Due to Cache Key Confusion 8.1 high 0.40.10-0.20260320084801-198a2bc82a99 20 Mar 2026
CVE-2021-32701: Incorrect Authorization in ORY Oathkeeper 7.5 high 0.38.12-beta.1 24 Jun 2021
OAuth2 Introspection Caching Bypass in Ory Oathkeeper 7.5 high 0.38.12-beta.1 23 Jun 2021
CVE-2026-33495: Ory Oathkeeper Authentication Bypass via Untrusted Header 6.5 medium 0.40.10-0.20260320084810-e9acca14a04d 20 Mar 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/ory/oathkeeper

Is github.com/ory/oathkeeper safe to use?

Vulert records 12 vulnerabilities for github.com/ory/oathkeeper in Go: 1 critical, 3 high, 1 medium and 1 low, plus 6 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/ory/oathkeeper's Vulert package health score?

Vulert scores github.com/ory/oathkeeper 65/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/ory/oathkeeper affected?

Yes. v0.40.9, the version you would install today, has 8 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/ory/oathkeeper should I use?

v1.0.0-beta.9 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/ory/oathkeeper have?

12 vulnerabilities are recorded for github.com/ory/oathkeeper in the Go ecosystem: 1 critical, 3 high, 1 medium and 1 low, plus 6 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/ory/oathkeeper vulnerabilities disclosed?

6 vulnerabilities were recorded for github.com/ory/oathkeeper in the last 12 months, and the oldest entry in this database dates to 23 Jun 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/ory/oathkeeper are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/ory/oathkeeper for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/ory/oathkeeper version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.