CyberSecBulletin
CVE-2026-47774NVD status: Analyzed

envoy: Asymmetric Resource Consumption (Amplification)

Published Updated By the CyberSecBulletin desk

CVE-2026-47774 is a high-severity asymmetric resource consumption (amplification) vulnerability in envoy from Envoyproxy, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected envoy versions: < 1.35.11; >= 1.36.0, < 1.36.7; >= 1.37.0, < 1.37.3, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.97% chance of exploitation within 30 days, higher than 62% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Openshift Service Mesh to 2.6.17 or 3.0.12 or 3.1.9 or 3.2.6, whichever matches your release line, or a later version.
  2. Read the advisory on github.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Envoyproxyenvoy< 1.35.11; >= 1.36.0, < 1.36.7; >= 1.37.0, < 1.37.3; >= 1.38.0, < 1.38.1Not stated
Red HatRed Hat OpenShift Service Mesh 2.6Not specified in the recordNot stated
Red HatRed Hat OpenShift Service Mesh 3.0Not specified in the recordNot stated
Red HatRed Hat OpenShift Service Mesh 3.1Not specified in the recordNot stated
Red HatRed Hat OpenShift Service Mesh 3.2Not specified in the recordNot stated
Red HatRed Hat OpenShift Service Mesh 3.3Not specified in the recordNot stated
Red HatOpenshift Service Mesh2.6 up to, but not including, 2.6.17; 3.0 up to, but not including, 3.0.12; 3.1 up to, but not including, 3.1.9; 3.2 up to, but not including, 3.2.6; 3.3 up to, but not including, 3.3.42.6.17, 3.0.12, 3.1.9, 3.2.6, 3.3.4

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (github.com).

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighCNA (github.com)
CVSS 3.17.5HighCNA

Official description

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 on encoded bytes without a corresponding limit on total decoded header size. Together, these behaviors allow a malicious client to cause large decoded header allocations while bypassing the intended request header size protections. Versions 1.35.11, 1.36.7, 1.37.3, and 1.38.1 contain a fix. No complete workaround is known short of applying a fix. Possible temporary mitigations include disabling downstream HTTP/2 where operationally feasible; enforcing stricter request header and cookie limits before traffic reaches Envoy; and monitoring Envoy memory usage for abnormal growth under HTTP/2 traffic.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Asymmetric Resource Consumption (Amplification)

The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is asymmetric.

How developers prevent this class of flaw

  • An application must make resources available to a client commensurate with the client's access level.
  • An application must, at all times, keep track of allocated resources and meter their usage appropriately.
  • Consider disabling resource-intensive algorithms on the server side, such as Diffie-Hellman key exchange.

More Asymmetric Resource Consumption (Amplification) vulnerabilities (CWE-405)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Technical write-ups (may include proof of concept)

Other vulnerabilities in envoy

All envoy vulnerabilities

Recent Asymmetric Resource Consumption (Amplification) vulnerabilities

Spotted an error? Tell us.