VMwareCVE-2026-59272
Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender
Medium6.8CVE-2026-59272 · Published Aug 27, 2026 · updated Sep 1, 2026
Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is exposed to man-in-the-middle interception of every log event. 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
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| Spring AMQP Product | <= 4.1.0 | No fix yet |
| >= 4.0.0, <= 4.0.4 | No fix yet | |
| >= 3.2.0, <= 3.2.12 | No fix yet | |
| <= 2.4.18 | No fix yet |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
- Severity from
- the vendor (its own CVE record or advisory)
- Weakness
- CWE-297
More VMware advisories
All VMware| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Aug 27 | VMware Spring AMQP: resource leak | Medium6.5 | No fix yet |
| Aug 27 | VMware Spring Integration: race condition | Medium4.2 | No fix yet |
| Aug 27 | VMware Spring Integration: improper input validation | Medium6.3 | No fix yet |
| Aug 27 | VMware Spring Integration: race condition | High8.2 | No fix yet |
| Aug 27 | VMware Spring Integration: unsafe deserialization | High8.0 | No fix yet |
| Aug 27 | VMware Spring Integration: link following | Medium6.8 | No fix yet |