# CVE-2021-32701: Incorrect Authorization in ORY Oathkeeper

Source: https://junglewise.ai/threats/cve-2021-32701-possible-bypass-of-token-claim-validation-when-oauth2  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2021-06-24  
License: CC BY 4.0 with a link back

CVE-2021-32701 · Severity: low · CVSS 3.1 · Published 2021-06-24

Incorrect Authorization in ORY Oathkeeper

Technologies: [github.com/ory/oathkeeper (Go)](https://junglewise.ai/threats/technologies/github-com-ory-oathkeeper). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2021-32701 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2021-32701 being exploited in the wild.

**How severe is CVE-2021-32701?** Low severity, with a CVSS score of 3.1, published 24 June 2021.

**Which products and versions are affected?** github.com/ory/oathkeeper (Go) SEMVER:introduced=0.38.0-beta.2,fixed=0.38.12-beta.1.

**Is there a fix for CVE-2021-32701?** Yes. github.com/ory/oathkeeper (Go): upgrade to 0.38.12-beta.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2021-32701?** 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.38.12-beta.1 or later

  ```sh
  go get github.com/ory/oathkeeper@v0.38.12-beta.1
  ```


## Affected products

- github.com/ory/oathkeeper (Go) SEMVER:introduced=0.38.0-beta.2,fixed=0.38.12-beta.1

## Identifiers

- CVE-2021-32701
- GHSA-qvp4-rpmr-xwrr
- GHSA-vfvf-6gx5-mqv6

## Related threats

- [GO-2026-4804 - Ory Oathkeeper has a path traversal authorization bypass in github.com/ory/oathkeeper](https://junglewise.ai/threats/cve-2026-33494-ory-oathkeeper-has-a-path-traversal-authorization-bypass)
- [GO-2026-4810 - Ory Oathkeeper has an authentication bypass by usage of untrusted header in github.com/ory/oathkeeper](https://junglewise.ai/threats/cve-2026-33495-ory-oathkeeper-has-an-authentication-bypass-by-usage-of-untrusted)
- [GO-2026-4799 - Ory Oathkeeper has an authentication bypass by cache key confusion in github.com/ory/oathkeeper](https://junglewise.ai/threats/cve-2026-33496-ory-oathkeeper-has-an-authentication-bypass-by-cache-key)
- [GO-2022-0920 - Incorrect Authorization in ORY Oathkeeper in github.com/ory/oathkeeper](https://junglewise.ai/threats/go-2022-0920-incorrect-authorization-in-ory-oathkeeper-in-github-com-837b4335)
- [GO-2022-0406 - Possible bypass of token claim validation when OAuth2 Introspection caching is enabled in…](https://junglewise.ai/threats/go-2022-0406-possible-bypass-of-token-claim-validation-when-oauth2-4bd5f14c)