Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.5.7 and 1.6.2, EnvoyExtensionPolicy Lua scripts executed by Envoy proxy can be used to leak the proxy's credentials. These credentials can then be used to communicate with the control plane and gain access to all secrets that are used by Envoy proxy, e.g. TLS private keys and credentials used for downstream and upstream communication. This vulnerability is fixed in 1.5.7 and 1.6.2.
Security readout for executives and security teams
Plain-English summary
Envoy Gateway versions before 1.5.7 and 1.6.2 can let a lower-privileged attacker abuse Lua extension policy scripts to expose proxy credentials. Those credentials may allow access to the control plane and secrets used by Envoy, including TLS private keys. This is a high-impact issue for environments using Envoy Gateway extension policies.
Executive priority
Prioritize remediation for production gateways, internet-facing gateways, and clusters where many services depend on Envoy-managed TLS or upstream credentials. The issue can affect confidentiality of private keys and credentials, so delayed patching may expand incident blast radius.
Technical view
CVE-2026-22771 affects envoyproxy/gateway <1.5.7 and >=1.6.0-rc.0,<1.6.2. EnvoyExtensionPolicy Lua scripts executed by Envoy proxy can leak proxy credentials. The advisory maps this to CWE-94 and CVSS 8.8, with network attack vector, low complexity, low privileges required, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in Kubernetes or standalone Envoy Gateway deployments running affected versions and using or allowing EnvoyExtensionPolicy Lua scripts. Systems not running Envoy Gateway, or already on 1.5.7 or 1.6.2, are not indicated as affected by the provided sources.
Exploitation context
The CVSS vector indicates network reachability, low attack complexity, and low privileges required. The provided sources do not state public exploitation, and the CVE is not marked as CISA KEV. The main risk is credential leakage leading to control plane access and exposure of Envoy-used secrets.
Researcher notes
The public description provides impact and fixed versions but limited operational detail. Avoid assuming arbitrary command execution beyond the stated credential leakage path. Validate exposure through version and EnvoyExtensionPolicy usage. No source in the bundle confirms active exploitation or provides a broader affected product list.
Mitigation direction
Upgrade Envoy Gateway to 1.5.7 or 1.6.2, per the advisory.
Identify and restrict who can create or modify EnvoyExtensionPolicy resources.
Review vendor guidance from Envoy and downstream distributors such as Red Hat.
Treat exposed proxy credentials and Envoy-used secrets as potentially compromised if exploitation is suspected.
Validation and detection
Inventory Envoy Gateway deployments and record exact versions.
Check for versions below 1.5.7 or 1.6.0-rc.0 through below 1.6.2.
Review clusters for EnvoyExtensionPolicy usage with Lua scripts.
Confirm upgraded deployments report version 1.5.7, 1.6.2, or later.
Review logs and secret access history for unusual control plane activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.