CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-22771 remediation guide

envoyproxy gateway, Red Hat Connectivity Link 1

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.

Open CVE record
Productenvoyproxy gateway, Red Hat Connectivity Link 1
Affected versions>= < 1.5.7, >= >= 1.6.0-rc.0, < 1.6.2, < 1.5.7, >= 1.6.0 < 1.6.2
Fixed versions1.5.7, 1.6.2
Priority basisReview · CVSS 8.8 · EPSS 0.57%
01

Identify the affected asset

Confirm whether envoyproxy gateway, Red Hat Connectivity Link 1 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= < 1.5.7, >= >= 1.6.0-rc.0, < 1.6.2, < 1.5.7, >= 1.6.0 < 1.6.2. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 1.5.7, 1.6.2. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.