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
A weakness in Envoy Gateway lets malicious Lua scripts in EnvoyExtensionPolicy expose proxy credentials. Those credentials may allow access to the control plane and secrets used by Envoy, including TLS private keys and communication credentials. Organizations using affected Envoy Gateway versions should treat this as a high-priority secrets exposure risk.
Executive priority
Prioritize remediation for internet-facing or multi-tenant gateway environments. The business risk is loss of proxy credentials and access to secrets, which can affect encrypted traffic and service-to-service trust.
Technical view
CVE-2026-22771 affects envoyproxy/gateway before 1.5.7 and 1.6.0-rc.0 through before 1.6.2. The issue is CWE-94 code injection in EnvoyExtensionPolicy Lua handling. CVSS 3.1 is 8.8: network attack vector, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where Envoy Gateway is deployed and EnvoyExtensionPolicy Lua scripts are enabled or manageable by non-administrative users. Affected versions are below 1.5.7, or 1.6.0-rc.0 through below 1.6.2.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The CVSS vector indicates exploitation is network-reachable with low privileges and no user interaction, but the bundle does not provide public exploit details.
Researcher notes
The title references arbitrary command execution, while the description emphasizes credential leakage through Lua script execution and subsequent control-plane secret access. Avoid assuming broader impact beyond the advisory text without vendor confirmation.
Mitigation direction
Upgrade Envoy Gateway to 1.5.7, 1.6.2, or later supported releases.
Review vendor advisory GHSA-xrwg-mqj6-6m22 for environment-specific guidance.
Restrict who can create or modify EnvoyExtensionPolicy resources.
Audit and rotate exposed Envoy proxy credentials if compromise is suspected.
Review access to TLS private keys and upstream/downstream credentials.
Validation and detection
Inventory Envoy Gateway versions across standalone and Kubernetes deployments.
Check for versions below 1.5.7 or 1.6.0-rc.0 through below 1.6.2.
Identify EnvoyExtensionPolicy usage and any Lua scripts in active configuration.
Review control-plane and secret-access logs for unusual Envoy credential use.
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.