Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, the OAuth2 HTTP filter's encrypt()/decrypt() functions use AES-256-CBC without an authentication tag (no HMAC, no AEAD). The /callback endpoint returns HTTP 302 on successful decryption and HTTP 401 on padding failure, creating a padding oracle. An attacker who obtains the encrypted CodeVerifier cookie can recover the plaintext PKCE code_verifier in ~6,200 requests (~100 seconds), then exchange it with a stolen authorization code to obtain the victim's access token. This vulnerability is fixed in 1.35.11, 1.36.7, 1.37.3, and 1.38.1.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-396h-jpq4-vc7p Exploit, Vendor Advisory, Mitigation
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-396h-jpq4-vc7p Exploit, Vendor Advisory, Mitigation
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.8 · envoyproxyNVD modified 2026-10-25 17:10
Affected (CPE criteria) 1
cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*
References 2
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-396h-jpq4-vc7p Exploit, Vendor Advisory, Mitigation
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-396h-jpq4-vc7p Exploit, Vendor Advisory, Mitigation