Quick answers
- Is CVE-2026-59272 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59272 being exploited in the wild.
- How severe is CVE-2026-59272?
- Medium severity, with a CVSS score of 6.8, published 27 August 2026.
- Which products and versions are affected?
- Spring AMQP 2.4.18 and earlier, 3.2.0–3.2.12, 4.0.0–4.0.4, 4.1.0.
- Is there a fix for CVE-2026-59272?
- 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-59272 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59272?
- Check whether you run 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 a TLS certificate validation bypass in Spring AMQP's RabbitMQ appender. Applications using Log4j2 with Spring AMQP to ship logs over TLS rely on documented defaults that disable proper certificate verification, leaving TLS connections vulnerable to man-in-the-middle (MITM) attacks. No authentication is required—any attacker positioned on the network path between the application and RabbitMQ broker can intercept encrypted log traffic. The affected versions include Spring AMQP 2.4.18 and earlier, 3.2.0–3.2.12, 4.0.0–4.0.4, and 4.1.0. Patches are expected to enforce certificate validation by default.
Affected products
- Spring AMQP 2.4.18 and earlier, 3.2.0–3.2.12, 4.0.0–4.0.4, 4.1.0
Timeline
- 2026-08-27: disclosed