CVE-2026-73547

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (46th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-84110 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's ext_authz filter assumes that a request contains a :path pseudoheader when applying query_parameters_to_set or query_parameters_to_remove from an authorization response. A path-less CONNECT request makes request_headers_->Path() return null, and Filter::onComplete dereferences that pointer while parsing the query string. An unauthenticated downstream client can crash the Envoy process when the filter and authorization response use query-parameter mutation. The relevant scope boundary is that the deployment must accept path-less CONNECT and configure ext_authz query-parameter mutation. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 21, 2026

Last Modified

October 6, 2026

Advisory Details (9)

Auto-updated Sep 21, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub release Patch Available

v1.39.1

Patch available: envoyproxy/envoy v1.39.1

https://github.com/envoyproxy/envoy/releases/tag/v1.39.1
GitHub release Patch Available

v1.38.4

Patch available: envoyproxy/envoy v1.38.4

https://github.com/envoyproxy/envoy/releases/tag/v1.38.4
GitHub release Patch Available

v1.37.6

Patch available: envoyproxy/envoy v1.37.6

https://github.com/envoyproxy/envoy/releases/tag/v1.37.6
GitHub release Patch Available

v1.36.10

Patch available: envoyproxy/envoy v1.36.10

https://github.com/envoyproxy/envoy/releases/tag/v1.36.10
GitHub commit

commit c3170d7c747e (envoyproxy/envoy)

Fix landed in envoyproxy/envoy commit c3170d7c747e — awaiting tagged release

https://github.com/envoyproxy/envoy/commit/c3170d7c747e51bb8254378ea89afc03d3e71929
GitHub commit

commit 838f8ffd9d7b (envoyproxy/envoy)

Fix landed in envoyproxy/envoy commit 838f8ffd9d7b — awaiting tagged release

https://github.com/envoyproxy/envoy/commit/838f8ffd9d7b5217682a22ee33470d4c7afb7e98
GitHub commit

commit 5f3b8e9b2b8a (envoyproxy/envoy)

Fix landed in envoyproxy/envoy commit 5f3b8e9b2b8a — awaiting tagged release

https://github.com/envoyproxy/envoy/commit/5f3b8e9b2b8a787a63202d35bb38820f3e9271fe
GitHub commit

commit 064af2e61d0d (envoyproxy/envoy)

Fix landed in envoyproxy/envoy commit 064af2e61d0d — awaiting tagged release

https://github.com/envoyproxy/envoy/commit/064af2e61d0d1c421490d9e3e6e643c5d117ffe4
GitHub advisoryMentions a patch (unverified)

ext_authz: request `:path` pseudoheader dereferenced w/o null check · Advisory · envoyproxy/envoy · GitHub

https://github.com/envoyproxy/envoy/security/advisories/GHSA-87ph-jqwm-pg6r

Patch Availability(5)

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(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 74× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 123 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 23 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-73547?
CVE-2026-73547 is a high-severity vulnerability; its CVE record was published on September 21, 2026. Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's ext_authz filter assumes that a request contains a :path pseudoheader when applying query_parameters_to_set or query_parameters_to_remove from an…
When was the CVE record for CVE-2026-73547 published?
The CVE record for CVE-2026-73547 was published on September 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-73547 actively exploited?
CVE-2026-73547 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73547?
CVE-2026-73547 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73547?
A fix for CVE-2026-73547 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73547 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-73547?

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