spring advanced message queuing protocol vulnerabilities and fixes

Recent CVEs affecting spring advanced message queuing protocol, with upgrade or downgrade steps. 5 tracked.

Also searched as: springadvancedmessagequeuingprotocol.

spring advanced message queuing protocol has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 5. Most recent: 2026-08-27. Highest priority: CVE-2026-59275 (score 33/100).

• CVE-2026-47860 MEDIUM 6.5 UPGRADE An attacker who can publish to a queue consumed by an application that has enabled message decompression can c
• CVE-2026-59271 MEDIUM 5.3 UPGRADE When the RabbitMQ management aliveness check fails, the configured admin password is embedded in cleartext in
• CVE-2026-59275 MEDIUM 6.6 UPGRADE A single hostile AMQP message can terminate the entire consumer JVM (System.exit(99)), not just the listener t
• CVE-2026-59272 MEDIUM 6.8 UPGRADE Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default,
• CVE-2026-59320 MEDIUM 6.5 UPGRADE When a container-level ErrorHandler is configured (the mitigation for finding 221000), each delivery whose pro

FAQ

How do I fix spring advanced message queuing protocol vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is spring advanced message queuing protocol being exploited right now?

None of the tracked spring advanced message queuing protocol CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which spring advanced message queuing protocol CVE should I patch first?

CVE-2026-59275 currently ranks highest (33/100): A single hostile AMQP message can terminate the entire consumer JVM (System.exit(99)), not just the listener t.

RSS feed for spring advanced message queuing protocol · ← Back to latest CVEs