Skip to main content
VulnerabilityPublished Updated

CVE-2026-41714: Spring AMQP · Improper Certificate Validation

Affects Spring AMQPSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.0 Medium · fixed in 4.0.3.1 : update Spring AMQP when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.3.1, 3.2.10.1, 3.1.16 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Spring AMQP to 4.0.3.1, 3.2.10.1, 3.1.16 or 2.4.18.

Affected software

ProductAffectedFixed in
SpringSpring AMQPAffected
  • >=4.0.0 <4.0.3.1
Fixed in
  • 4.0.3.1
SpringSpring AMQPAffected
  • >=3.2.0 <3.2.10.1
Fixed in
  • 3.2.10.1
SpringSpring AMQPAffected
  • >=3.1.0 <3.1.16
Fixed in
  • 3.1.16
SpringSpring AMQPAffected
  • >=2.4.0 <2.4.18
Fixed in
  • 2.4.18
Mavenorg.springframework.amqp/spring-amqppkg:maven/org.springframework.amqp/spring-amqpOther threatsAffected
  • 2.4.0 – 4.0.4
8 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, ensure that applications explicitly call setUseSSL(true) when configuring RabbitConnectionFactoryBean with an amqps URI to enable proper certificate validation and hostname verification. Avoid relying solely on setUri("amqps://...") without this additional configuration.

Description

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.

References

Community reviews

Loading reviews…