CVE-2026-41708

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-15. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, 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: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

In Spring Cloud Sleuth, it is possible for a user to provide specially crafted calls that may cause a denial-of-service (DoS) condition. The application is vulnerable when it uses a vulnerable version of org.springframework.cloud:spring-cloud-sleuth-instrumentation and Spring TX instrumentation is not disabled.

Affected versions: Spring Cloud Sleuth 3.1.0 through 3.1.13.

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%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026
No patch confirmed yet.
generic

CVE-2026-41708: Spring Cloud Sleuth instrumentation of Spring TX DoS vulnerability

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

Vendor Advisories for CVE-2026-41708(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 14× in last 7d / 72× 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 111 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-41708?
CVE-2026-41708 is a high vulnerability published on June 15, 2026. In Spring Cloud Sleuth, it is possible for a user to provide specially crafted calls that may cause a denial-of-service (DoS) condition. The application is vulnerable when it uses a vulnerable version of org.springframework.cloud:spring-cloud-sleuth-instrumentation and Spring TX instrumentation is…
When was CVE-2026-41708 disclosed?
CVE-2026-41708 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41708 actively exploited?
CVE-2026-41708 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.0% of all scored CVEs.
What is the CVSS score of CVE-2026-41708?
CVE-2026-41708 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-41708?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41708, 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-41708

Explore →

Is Your Infrastructure Affected by CVE-2026-41708?

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