Skip to main content
VulnerabilityPublished Updated

CVE-2026-41701: Spring AMQP · Weak Randomness

Affects Spring AMQPSource CVE Database V5

0
Compare

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

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
4.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% 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 +3
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/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 29 Oct 2026.

What to do

Upgrade Spring AMQP to 4.0.3.1, 3.2.10.1, 3.1.16 or 2.4.18; org.springframework.amqp/spring-amqp to 4.0.4, 3.2.11, 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 <2.4.18
  • 3.1.0 <3.1.16
  • 3.2.0 <3.2.11
  • 4.0.0 <4.0.4
Fixed in
  • 2.4.18
  • 3.1.16
  • 3.2.11
  • 4.0.4

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, consider avoiding the use of fixed reply queues with RabbitTemplate.sendAndReceive() or implement additional application-level randomness or correlation ID management to mitigate predictability.

Description

Correlation IDs for replies in the RabbitTemplate.sendAndReceive() with the fixed reply queue are predictable due to internal simple counter. 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…