Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-47775

Envoy OAuth2 Filter: Padding Oracle via AES-256-CBC Cookie Decryption

Overview

Published
26 Jun 2026
Modified
25 Oct 2026
Medium CVE
1 Registry packages
3 OS packages
1 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

6.8 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Weakness: CWE-209, CWE-327

Affected packages · 1

Packages affected by CVE-2026-47775
EcosystemPackageVulnerableFixed in
Bitnami envoy <1.35.11>=1.36.0, <1.36.7>=1.37.0, <1.37.3>=1.38.0, <1.38.1 1.35.111.36.71.37.31.38.1

Open a package to see all its vulnerabilities.

Operating systems · 1 fix

openSUSE 1 release · 1 package

fixed 1
istioctl
openSUSE fixes for CVE-2026-47775
ReleasePackageFixed inAdvisory
Tumbleweed istioctl +2 1.30.2-1.1 openSUSE-SU-2026:11141-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.