CVE-2026-47774

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0%, top 41% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
59%
KEV
Not listed

Published

June 17, 2026

Last Modified

July 20, 2026

Advisory Details (2)

Auto-updated Jun 17, 2026
Patch available. Sources: github.
generic

oss-security - Re: HTTP/2 Bomb affects Apache httpd, nginx, envoy, & pingora

http://www.openwall.com/lists/oss-security/2026/06/04/15
github Patch Available

HTTP/2 memory exhaustion via cookie header size bypass and HPACK amplification · Advisory · envoyproxy/envoy · GitHub

https://github.com/envoyproxy/envoy/security/advisories/GHSA-22m2-hvr2-xqc8

Vendor Advisories for CVE-2026-47774(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift-service-mesh/proxyv2-rhel9:17816047242026-06-18redhat
redhatopenshift-service-mesh/istio-proxyv2-rhel9:17810699082026-06-16redhat
redhatopenshift-service-mesh/istio-proxyv2-rhel9:17810701582026-06-16redhat
redhatopenshift-service-mesh/istio-proxyv2-rhel9:17810709672026-06-16redhat
redhatopenshift-service-mesh/istio-proxyv2-rhel9:17810945202026-06-16redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 23× in last 7d / 94× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 189 total refreshes for this CVE.

  1. 2026-08-21 10:23 UTCEG score recompute
  2. 2026-08-21 10:23 UTCVendor advisory
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 21:17 UTCVendor advisory
  5. 2026-08-20 08:13 UTCEG score recompute
  6. 2026-08-20 08:13 UTCVendor advisory
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 08:09 UTCEG score recompute
  9. 2026-08-19 08:09 UTCVendor advisory
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 10:03 UTCVendor advisory
  13. 2026-08-16 21:00 UTCEG score recompute
  14. 2026-08-16 21:00 UTCVendor advisory
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 06:19 UTCEG score recompute
  17. 2026-08-16 06:19 UTCVendor advisory
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 17:16 UTCVendor advisory
  20. 2026-08-15 04:07 UTCEG score recompute
  21. 2026-08-15 04:07 UTCVendor advisory
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 15:03 UTCVendor advisory
  24. 2026-08-14 02:00 UTCEG score recompute
  25. 2026-08-14 02:00 UTCVendor advisory
Show 75 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 12:56 UTCVendor advisory
  3. 2026-08-12 23:52 UTCEG score recompute
  4. 2026-08-12 23:52 UTCVendor advisory
  5. 2026-08-12 13:51 UTCEPSS rescore
  6. 2026-08-12 10:49 UTCVendor advisory
  7. 2026-08-11 21:45 UTCEG score recompute
  8. 2026-08-11 21:45 UTCVendor advisory
  9. 2026-08-11 08:41 UTCEG score recompute
  10. 2026-08-11 08:41 UTCVendor advisory
  11. 2026-08-11 00:00 UTCEPSS rescore
  12. 2026-08-10 19:38 UTCVendor advisory
  13. 2026-08-10 06:34 UTCVendor advisory
  14. 2026-08-09 17:30 UTCEG score recompute
  15. 2026-08-09 17:30 UTCVendor advisory
  16. 2026-08-09 13:46 UTCEPSS rescore
  17. 2026-08-09 04:26 UTCEG score recompute
  18. 2026-08-09 04:26 UTCVendor advisory
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-08 15:23 UTCVendor advisory
  21. 2026-08-08 02:19 UTCEG score recompute
  22. 2026-08-08 02:19 UTCVendor advisory
  23. 2026-08-07 13:15 UTCVendor advisory
  24. 2026-08-07 00:11 UTCEG score recompute
  25. 2026-08-07 00:11 UTCVendor advisory
  26. 2026-08-06 13:47 UTCEPSS rescore
  27. 2026-08-06 11:08 UTCVendor advisory
  28. 2026-08-05 22:04 UTCEG score recompute
  29. 2026-08-05 22:04 UTCVendor advisory
  30. 2026-08-05 19:17 UTCEPSS rescore
  31. 2026-08-05 09:00 UTCVendor advisory
  32. 2026-08-04 15:25 UTCEG score recompute
  33. 2026-08-04 15:25 UTCVendor advisory
  34. 2026-08-04 15:10 UTCEPSS rescore
  35. 2026-08-04 10:39 UTCEPSS rescore
  36. 2026-08-03 22:40 UTCEG score recompute
  37. 2026-08-03 22:40 UTCVendor advisory
  38. 2026-08-03 10:36 UTCEPSS rescore
  39. 2026-08-03 09:37 UTCVendor advisory
  40. 2026-08-02 20:32 UTCVendor advisory
  41. 2026-08-02 07:28 UTCEG score recompute
  42. 2026-08-02 07:28 UTCVendor advisory
  43. 2026-08-02 02:27 UTCEPSS rescore
  44. 2026-08-01 18:24 UTCVendor advisory
  45. 2026-08-01 05:20 UTCEG score recompute
  46. 2026-08-01 05:20 UTCVendor advisory
  47. 2026-08-01 04:16 UTCEPSS rescore
  48. 2026-07-31 11:57 UTCVendor advisory
  49. 2026-07-30 22:37 UTCEG score recompute
  50. 2026-07-30 22:37 UTCVendor advisory
  51. 2026-07-30 16:28 UTCEPSS rescore
  52. 2026-07-30 04:22 UTCEG score recompute
  53. 2026-07-30 04:22 UTCVendor advisory
  54. 2026-07-30 01:30 UTCEPSS rescore
  55. 2026-07-29 15:14 UTCVendor advisory
  56. 2026-07-29 02:07 UTCEG score recompute
  57. 2026-07-29 02:07 UTCVendor advisory
  58. 2026-07-28 15:37 UTCEPSS rescore
  59. 2026-07-28 01:12 UTCEG score recompute
  60. 2026-07-28 01:12 UTCVendor advisory
  61. 2026-07-27 08:08 UTCVendor advisory
  62. 2026-07-26 19:04 UTCEG score recompute
  63. 2026-07-26 19:04 UTCVendor advisory
  64. 2026-07-26 14:54 UTCEPSS rescore
  65. 2026-07-25 14:18 UTCEPSS rescore
  66. 2026-07-24 14:18 UTCEPSS rescore
  67. 2026-07-23 14:18 UTCEPSS rescore
  68. 2026-07-23 03:17 UTCEG score recompute
  69. 2026-07-22 14:08 UTCEPSS rescore
  70. 2026-07-21 15:24 UTCEPSS rescore
  71. 2026-07-20 17:08 UTCEPSS rescore
  72. 2026-07-19 14:31 UTCEPSS rescore
  73. 2026-07-19 02:29 UTCEPSS rescore
  74. 2026-07-18 10:04 UTCEPSS rescore
  75. 2026-07-16 21:41 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-47774?
CVE-2026-47774 is a high vulnerability published on June 17, 2026. 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…
When was CVE-2026-47774 disclosed?
CVE-2026-47774 was first published in the National Vulnerability Database on June 17, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47774 actively exploited?
CVE-2026-47774 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 41.0% of all scored CVEs.
What is the CVSS score of CVE-2026-47774?
CVE-2026-47774 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-47774?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47774, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-47774

Explore →

Is Your Infrastructure Affected by CVE-2026-47774?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs