CVE-2026-59323

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory published 2026-08-21. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VMware by Broadcom) lists Spring Micrometer Tracing versions 1.6.0 up to and including 1.6.6, 1.5.0 up to and including 1.5.12 and up to and including 1.4.13 as affected. No release containing a fix is confirmed on record.

An application using Micrometer Tracing with W3C baggage propagation in the Brave bridge is vulnerable to denial of service (DoS) due to unbounded object allocation when extracting incoming baggage headers. Micrometer Tracing 1.7.0 Micrometer Tracing 1.6.0 - 1.6.6 Micrometer Tracing 1.5.0 - 1.5.12 Micrometer Tracing 1.4.13 and earlier

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

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 (value × EchelonGraph’s weight)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation0.4% × 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

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.

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

August 21, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 21, 2026
No fix on record yet.
Web page

Micrometer Tracing Brave Bridge W3C Baggage propagation DoS vulnerability

https://spring.io/security/cve-2026-59323

Vendor Advisories for CVE-2026-59323(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× 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 136 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 36 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59323?
CVE-2026-59323 is a medium-severity vulnerability; its CVE record was published on August 21, 2026. An application using Micrometer Tracing with W3C baggage propagation in the Brave bridge is vulnerable to denial of service (DoS) due to unbounded object allocation when extracting incoming baggage headers. Micrometer Tracing 1.7.0 Micrometer Tracing 1.6.0 - 1.6.6 Micrometer Tracing 1.5.0 - 1.5.12…
When was the CVE record for CVE-2026-59323 published?
The CVE record for CVE-2026-59323 was published on August 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 August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-59323 actively exploited?
CVE-2026-59323 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59323?
CVE-2026-59323 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59323?
No fix for CVE-2026-59323 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VMware by Broadcom) lists Spring Micrometer Tracing versions 1.6.0 up to and including 1.6.6, 1.5.0 up to and including 1.5.12 and up to and including 1.4.13 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-59323 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59323?

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

Book a Demo →Browse All CVEs