CVE-2026-41717

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

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

Spring Data MongoDB contains a SpEL (Spring Expression Language) expression injection vulnerability. The issue occurs during parameter binding when a user-defined repository query method is annotated with @Query and utilizes a capture-all placeholder.

Affected versions: Spring Data MongoDB 5.0.0 through 5.0.5; 4.5.0 through 4.5.11; 4.4.0 through 4.4.14; 4.3.0 through 4.3.16; 4.2.0 through 4.2.15; 4.1.0 through 4.1.14; 4.0.0 through 4.0.15; 3.4.0 through 3.4.19.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
25.2%
KEV
Not listed

Published

June 10, 2026

Last Modified

July 17, 2026

Advisory Details (1)

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

CVE-2026-41717: Spring Data MongoDB - SpEL Expression Injection via Annotated Query Parameter Binding

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

Vendor Advisories for CVE-2026-41717(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 9× in last 7d / 77× 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 121 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-41717?
CVE-2026-41717 is a high vulnerability published on June 10, 2026. Spring Data MongoDB contains a SpEL (Spring Expression Language) expression injection vulnerability. The issue occurs during parameter binding when a user-defined repository query method is annotated with @Query and utilizes a capture-all placeholder. Affected versions: Spring Data MongoDB 5.0.0…
When was CVE-2026-41717 disclosed?
CVE-2026-41717 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on July 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-41717 actively exploited?
CVE-2026-41717 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41717?
CVE-2026-41717 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-41717?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41717, 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-41717

Explore →

Is Your Infrastructure Affected by CVE-2026-41717?

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

Start Free Scan →Browse All CVEs