CVE-2026-47774 remediation guide
envoyproxy envoy, Red Hat OpenShift Service Mesh 2.6, Red Hat OpenShift Service Mesh 3.0
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to versions 1.35.11, 1.36.7, 1.37.3, and 1.38.1, a vulnerability in Envoy's HTTP/2 downstream request processing allows an unauthenticated remote client to trigger excessive memory consumption, potentially resulting in OOM termination of the Envoy process and denial of service. The issue arises from the combination of two behaviors. First, cookie header bytes are not fully accounted for during request header size validation in Envoy. Second, HPACK header block limits in oghttp2/quiche are enforced o...
Identify the affected asset
Confirm whether envoyproxy envoy, Red Hat OpenShift Service Mesh 2.6, Red Hat OpenShift Service Mesh 3.0 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.
Validate the affected-version match
Compare the deployed version with the affected range: >= < 1.35.11, >= >= 1.36.0, < 1.36.7, >= >= 1.37.0, < 1.37.3, >= >= 1.38.0, < 1.38.1, < 1.35.11, >= 1.36.0 < 1.36.7, >= 1.37.0 < 1.37.3, 1.38.0, >= 2.6 < 2.6.17, >= 3.0 < 3.0.12, >= 3.1 < 3.1.9, >= 3.2 < 3.2.6, >= 3.3 < 3.3.4. Treat incomplete inventory results as unresolved.
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.
Apply supported remediation
Follow the vendor advisory or supported update path. Current fixed-version status: 1.35.11, 1.36.7, 1.37.3, 2.6.17, 3.0.12, 3.1.9, 3.2.6, 3.3.4. Preserve configuration and rollback material before change.
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.