CVE-2026-41714

MEDIUMPre-NVD 4.04.0
EchelonGraph scoreHIGH confidence

Score 4.0 from GitHub Security Advisory published 2026-06-10. a secondary CVSS source baseline 4.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
4.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.0Exploit: NoneExposed: 0

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

Applications that configure their broker connection via RabbitConnectionFactoryBean.setUri("amqps://...") without also calling setUseSSL(true) get TLS encryption with no certificate validation and no hostname verification.

Affected versions: Spring AMQP 4.0.0 through 4.0.3; 3.2.0 through 3.2.10; 3.1.0 through 3.1.15; 2.4.0 through 2.4.17.

CVSS v3
4.0
EG Score
4.0(high)
EPSS
3.1%
KEV
Not listed

Published

June 10, 2026

Last Modified

June 27, 2026

Advisory Details (1)

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

CVE-2026-41714: In Spring AMQP the `RabbitConnectionFactoryBean.setUri("amqps://...")` bypasses secure SSL setup, uses `TrustEverythingTrustManager`

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

Vendor Advisories for CVE-2026-41714(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 / 78× 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.

  1. 2026-07-06 02:23 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 14:12 UTCEG score recompute
  4. 2026-07-05 14:12 UTCGHSA enrichment
  5. 2026-07-04 12:47 UTCEG score recompute
  6. 2026-07-04 12:47 UTCGHSA enrichment
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-03 09:37 UTCEG score recompute
  9. 2026-07-03 09:37 UTCGHSA enrichment
  10. 2026-07-02 08:14 UTCEG score recompute
  11. 2026-07-02 08:13 UTCGHSA enrichment
  12. 2026-07-01 06:45 UTCEG score recompute
  13. 2026-07-01 06:45 UTCGHSA enrichment
  14. 2026-06-30 23:22 UTCEPSS rescore
  15. 2026-06-30 05:20 UTCEG score recompute
  16. 2026-06-30 05:20 UTCGHSA enrichment
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 03:38 UTCEG score recompute
  19. 2026-06-29 03:38 UTCGHSA enrichment
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-28 02:09 UTCEG score recompute
  23. 2026-06-28 02:09 UTCGHSA enrichment
  24. 2026-06-27 03:08 UTCEPSS rescore
  25. 2026-06-27 00:45 UTCEG score recompute
Show 53 more
  1. 2026-06-27 00:45 UTCGHSA enrichment
  2. 2026-06-25 23:18 UTCEG score recompute
  3. 2026-06-25 23:18 UTCGHSA enrichment
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 21:53 UTCEG score recompute
  7. 2026-06-24 21:53 UTCGHSA enrichment
  8. 2026-06-24 14:05 UTCEPSS rescore
  9. 2026-06-23 21:33 UTCEPSS rescore
  10. 2026-06-23 20:29 UTCEG score recompute
  11. 2026-06-23 20:29 UTCGHSA enrichment
  12. 2026-06-22 18:46 UTCEG score recompute
  13. 2026-06-22 18:46 UTCGHSA enrichment
  14. 2026-06-22 14:25 UTCEPSS rescore
  15. 2026-06-22 14:25 UTCEPSS rescore
  16. 2026-06-21 17:19 UTCEG score recompute
  17. 2026-06-21 17:19 UTCGHSA enrichment
  18. 2026-06-21 14:56 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 01:59 UTCEPSS rescore
  21. 2026-06-20 15:46 UTCEG score recompute
  22. 2026-06-20 15:46 UTCGHSA enrichment
  23. 2026-06-19 19:25 UTCEPSS rescore
  24. 2026-06-19 14:06 UTCEG score recompute
  25. 2026-06-19 14:06 UTCGHSA enrichment
  26. 2026-06-18 17:52 UTCEPSS rescore
  27. 2026-06-18 17:52 UTCEPSS rescore
  28. 2026-06-18 12:40 UTCEG score recompute
  29. 2026-06-18 12:40 UTCGHSA enrichment
  30. 2026-06-17 17:53 UTCEPSS rescore
  31. 2026-06-17 11:14 UTCEG score recompute
  32. 2026-06-17 11:13 UTCGHSA enrichment
  33. 2026-06-16 17:52 UTCEPSS rescore
  34. 2026-06-16 09:49 UTCEG score recompute
  35. 2026-06-16 09:49 UTCGHSA enrichment
  36. 2026-06-15 17:49 UTCEPSS rescore
  37. 2026-06-15 08:25 UTCEG score recompute
  38. 2026-06-15 08:25 UTCGHSA enrichment
  39. 2026-06-14 06:56 UTCEG score recompute
  40. 2026-06-14 06:56 UTCGHSA enrichment
  41. 2026-06-13 23:00 UTCEPSS rescore
  42. 2026-06-13 05:30 UTCEG score recompute
  43. 2026-06-13 05:30 UTCGHSA enrichment
  44. 2026-06-12 23:12 UTCEPSS rescore
  45. 2026-06-12 23:12 UTCEPSS rescore
  46. 2026-06-12 04:06 UTCEG score recompute
  47. 2026-06-12 04:06 UTCGHSA enrichment
  48. 2026-06-11 14:00 UTCEPSS rescore
  49. 2026-06-11 02:42 UTCEG score recompute
  50. 2026-06-11 02:42 UTCGHSA enrichment
  51. 2026-06-10 22:18 UTCEPSS rescore
  52. 2026-06-10 01:18 UTCEG score recompute
  53. 2026-06-10 01:18 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-41714?
CVE-2026-41714 is a medium vulnerability published on June 10, 2026. Applications that configure their broker connection via RabbitConnectionFactoryBean.setUri("amqps://...") without also calling setUseSSL(true) get TLS encryption with no certificate validation and no hostname verification. Affected versions: Spring AMQP 4.0.0 through 4.0.3; 3.2.0 through 3.2.10;…
When was CVE-2026-41714 disclosed?
CVE-2026-41714 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on June 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41714 actively exploited?
CVE-2026-41714 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41714?
CVE-2026-41714 has a CVSS v3 base score of 4.0 (NVD).
How do I remediate CVE-2026-41714?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41714, 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-41714

Explore →

Is Your Infrastructure Affected by CVE-2026-41714?

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