Quick answers
- Is CVE-2026-59271 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59271 being exploited in the wild.
- How severe is CVE-2026-59271?
- Medium severity, with a CVSS score of 5.3, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring AMQP 4.1.0, 4.0.0–4.0.4, 3.2.0–3.2.12, 2.4.18 and earlier.
- Is there a fix for CVE-2026-59271?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-59271 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-59271?
- Check whether you run VMware Spring AMQP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an information disclosure flaw in Spring AMQP's RabbitMQ management connectivity check. When the aliveness check fails, the underlying exception message contains the plaintext admin password instead of being redacted or obfuscated. The vulnerability affects Spring AMQP 4.1.0, 4.0.0–4.0.4, 3.2.0–3.2.12, and 2.4.18 and earlier versions. No special authentication or network access preconditions are required beyond normal application operation; any application logs or error monitoring systems that capture exception messages will expose the credentials. A fix is available in patched versions of Spring AMQP.
Affected products
- VMware Spring AMQP 4.1.0, 4.0.0–4.0.4, 3.2.0–3.2.12, 2.4.18 and earlier
Timeline
- 2026-08-27: disclosed
- 2026-08-27: advisory