ORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP…
Historical advisory recorded 24 Oct 2026 18:17:28 UTC. Read the latest advisory.
nvd · CVE-2021-32701
PublishedORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. When you make a request to an endpoint that requires the scope `foo` using an access token granted with that `foo` scope, introspection will be valid and that token will be cached. The problem comes when a second requests to an endpoint that requires the scope `bar` is made before the cache has expired. Whether the token is granted or not to the `bar` scope, introspection will be valid. A patch will be released with `v0.38.12-beta.1`. Per default, caching is disabled for the `oauth2_introspection` authenticator. When caching is disabled, this vulnerability does not exist. The cache is checked in [`func (a *AuthenticatorOAuth2Introspection) Authenticate(...)`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L152). From [`tokenFromCache()`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L97) it seems that it only validates the token expiration date, but ignores whether the token has or not the proper scopes. The vulnerability was introduced in PR #424. During review, we failed to require appropriate test coverage by the submitter which is the primary reason that the vulnerability passed the review process.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2021-32701
PublishedORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. When you make a request to an endpoint that requires the scope `foo` using an access token grant…
ORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. When you make a request to an endpoint that requires the scope `foo` using an access token granted with that `foo` scope, introspection will be valid and that token will be cached. The problem comes when a second requests to an endpoint that requires the scope `bar` is made before the cache has expired. Whether the token is granted or not to the `bar` scope, introspection will be valid. A patch will be released with `v0.38.12-beta.1`. Per default, caching is disabled for the `oauth2_introspection` authenticator. When caching is disabled, this vulnerability does not exist. The cache is checked in [`func (a *AuthenticatorOAuth2Introspection) Authenticate(...)`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L152). From [`tokenFromCache()`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L97) it seems that it only validates the token expiration date, but ignores whether the token has or not the proper scopes. The vulnerability was introduced in PR #424. During review, we failed to require appropriate test coverage by the submitter which is the primary reason that the vulnerability passed the review process.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-863
Original publisher date fields
published: 2021-06-22T20:15:08.727
lastModified: 2026-06-17T03:53:27.340
12 source CPE criteria · context only
- cpe:2.3:a:ory:oathkeeper:0.38.0:beta2:*:*:*:*:*:*
- cpe:2.3:a:ory:oathkeeper:0.38.1:beta2:*:*:*:*:*:*
- cpe:2.3:a:ory:oathkeeper:0.38.2:beta1:*:*:*:*:*:*
- cpe:2.3:a:ory:oathkeeper:0.38.3:beta1:*:*:*:*:*:*
- cpe:2.3:a:ory:oathkeeper:0.38.4:beta1:*:*:*:*:*:*
- cpe:2.3:a:ory:oathkeeper:0.38.5:beta1:*:*:*:*:*:*
- cpe:2.3:a:ory:oathkeeper:0.38.6:beta1:*:*:*:*:*:*
- cpe:2.3:a:ory:oathkeeper:0.38.7:beta1:*:*:*:*:*:*
- cpe:2.3:a:ory:oathkeeper:0.38.8:beta1:*:*:*:*:*:*
- cpe:2.3:a:ory:oathkeeper:0.38.9:beta1:*:*:*:*:*:*
- cpe:2.3:a:ory:oathkeeper:0.38.10:beta2:*:*:*:*:*:*
- cpe:2.3:a:ory:oathkeeper:0.38.11:beta1:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 22 Jun 2021 20:15:08 UTC
- Source modified
- 17 Jun 2026 03:53:27 UTC
- Saved here
- 24 Oct 2026 18:17:28 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 3.1 · [email protected] · Primary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.0 · [email protected] · Primary · 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N