Ory Oathkeeper has an authentication bypass by cache key confusion

高 8.1CVE-2026-33496 · GHSA-4mq7-pvjg-xp2r · GO-2026-4799 · 26/03/2026 公開 · 17/06/2026 更新

要点

CVE-2026-33496 は github.com/ory/oathkeeper, oathkeeper (ory) に影響する深刻度「高」 (CVSS 8.1) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.38%（全脆弱性の 32.5% より高い）。
対処：0.40.10-0.20260320084801-198a2bc82a99, 26.2.0 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
github.com/ory/oathkeeper Go	`< 0.40.10-0.20260320084801-198a2bc82a99`	`0.40.10-0.20260320084801-198a2bc82a99`
oathkeeper ory	`< 26.2.0`	`26.2.0`

概要

Description

Ory Oathkeeper is vulnerable to authentication bypass due to cache key confusion. The oauth2_introspection authenticator cache does not distinguish tokens that were validated with different introspection URLs. An attacker can therefore legitimately use a token to prime the cache, and subsequently use the same token for rules that use a different introspection server.

Preconditions

Ory Oathkeeper has to be configured with multiple oauth2_introspection authenticator servers, each accepting different tokens. The authenticators also must be configured to use caching. An attacker has to have a way to gain a valid token for one of the configured introspection servers.

Mitigation

Ory Oathkeeper now includes the introspection server URL in the cache key, preventing confusion of tokens.

Update to the patched version of Ory Oathkeeper. If that is not immediately possible, disable caching for oauth2_introspection authenticators.

NVD の説明

ORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. Versions prior to 26.2.0 are vulnerable to authentication bypass due to cache key confusion. The `oauth2_introspection` authenticator cache does not distinguish tokens that were validated with different introspection URLs. An attacker can therefore legitimately use a token to prime the cache, and subsequently use the same token for rules that use a different introspection server. Ory Oathkeeper has to be configured with multiple `oauth2_introspection` authenticator servers, each accepting different tokens. The authenticators also must be configured to use caching. An attacker has to have a way to gain a valid token for one of the configured introspection servers. Starting in version 26.2.0, Ory Oathkeeper includes the introspection server URL in the cache key, preventing confusion of tokens. Update to the patched version of Ory Oathkeeper. If that is not immediately possible, disable caching for `oauth2_introspection` authenticators.