CVE-2026-40984

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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.1%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In Micrometer, it is possible for a user to provide specially crafted HTTP requests that may cause a denial-of-service (DoS) condition.

Affected versions: micrometer-core 1.16.0 through 1.16.5; 1.15.0 through 1.15.11; 1.14.0 through 1.14.15; 1.13.0 through 1.13.18; 1.9.0 through 1.9.17. micrometer-jetty11 1.16.0 through 1.16.5; 1.15.0 through 1.15.11; 1.14.0 through 1.14.15; 1.13.0 through 1.13.18. micrometer-jetty12 1.16.0 through 1.16.5; 1.15.0 through 1.15.11; 1.14.0 through 1.14.15; 1.13.0 through 1.13.18.

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 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%
EPSS PROB
1.1%
EPSS %ILE
63rd
KEV
Not listed

Published

June 9, 2026

Last Modified

September 14, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Patch available.
generic

CVE-2026-40984: Micrometer HTTP server instrumentations DoS vulnerability

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

Vendor Advisories for CVE-2026-40984(11)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatmicrometer-core2026-09-10redhat
redhatdevspaces/pluginregistry-rhel9:17877597232026-09-01redhat
redhatrhbk/keycloak-rhel9-operator:26.6-112026-08-05redhat
redhatrhbk-rhel9-operator/rhbk-rhel9-operator2026-08-05redhat

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.

Affected Packages

(3 across 1 ecosystem)
Maven(3)
PackageVulnerable rangeFix by version rangeDependents
io.micrometer:micrometer-core0.10.0.RELEASE ... 1.9.9 (153 versions)
  • 1.16.0 up to 1.16.6: fixed in 1.16.6
  • 1.15.0 up to 1.15.12: fixed in 1.15.12
  • 1.14.0 through 1.14.14: no fix on record
  • 1.10.0 through 1.13.15: no fix on record
  • every version through 1.9.17: no fix on record
—
io.micrometer:micrometer-jetty111.10.0 ... 1.13.9 (57 versions)
  • 1.16.0 up to 1.16.6: fixed in 1.16.6
  • 1.15.0 up to 1.15.12: fixed in 1.15.12
  • 1.14.0 through 1.14.14: no fix on record
  • every version through 1.13.15: no fix on record
—
io.micrometer:micrometer-jetty121.13.0 ... 1.13.9 (16 versions)
  • 1.16.0 up to 1.16.6: fixed in 1.16.6
  • 1.15.0 up to 1.15.12: fixed in 1.15.12
  • 1.14.0 through 1.14.14: no fix on record
  • every version through 1.13.15: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 31× 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 297 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Same product

1 shown

Maven:io.micrometer:micrometer-core

Frequently asked(5)

What is CVE-2026-40984?
CVE-2026-40984 is a high vulnerability published on June 9, 2026. In Micrometer, it is possible for a user to provide specially crafted HTTP requests that may cause a denial-of-service (DoS) condition. Affected versions: micrometer-core 1.16.0 through 1.16.5; 1.15.0 through 1.15.11; 1.14.0 through 1.14.15; 1.13.0 through 1.13.18; 1.9.0 through 1.9.17.…
When was CVE-2026-40984 disclosed?
CVE-2026-40984 was first published on June 9, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40984 actively exploited?
CVE-2026-40984 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (63rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-40984?
CVE-2026-40984 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-40984?
A fix for CVE-2026-40984 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-40984 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40984

Explore →

Is Your Infrastructure Affected by CVE-2026-40984?

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

Book a Demo →Browse All CVEs