Admin password disclosed in BrokerNotAliveException message

published 2026-08-27 2 mo ago modified 2026-09-01 2 mo ago also EUVD-2026-66847

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits: 0; none known

When the RabbitMQ management aliveness check fails, the configured admin password is embedded in cleartext in the thrown exception message. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier

Patch / fix

fixed in 1

vmware spring_advanced_message_queuing_protocol 2.4.19, 3.2.13, 4.0.4.1, 4.1.0.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-59271 updated 2026-11-04 cvss 5.3

org.springframework.amqp/spring-amqp: Spring AMQP: Admin password disclosure via exception message

Red Hat build of Apache Camel 4 for Quarkus 3 spring-amqp 3.2.9
affected: workaround, no fix available “Fix deferred”
Red Hat Fuse 7 spring-amqp 3.2.9
affected: workaround, no fix planned “Out of support scope”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 2 mo ago (2026-08-27)

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected products

Spring Spring AMQP

Classification

Weakness

CWE-209 Generation of Error Message Containing Sensitive Information

References

spring.io /security/cve-2026-59271
vendor-advisory

Sources

CVE List CVE-2026-59271
NVD CVE-2026-59271

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary