CVE-2026-59272Log4j2 AmqpAppender disables TLS hostname verification by default
Updated under an hour ago ()
Does this affect you?
It affects Spring AMQP and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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
- CVSS
- 6.8 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
- Weakness (CWE)
- CWE-297
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- vmware
- NVD analysis
- Analyzed
- Record last updated
- Aug 28, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Spring Spring AMQP spring:amqp (from the name) | 4.1.0; from 4.0.0 through 4.0.4; from 3.2.0 through 3.2.12; through 2.4.18 | CNA record |
vmware spring_advanced_message_queuing_protocol vmware:spring_advanced_message_queuing_protocol | before 2.4.19; from 3.2.0 before 3.2.13; from 4.0.0 before 4.0.4.1; from 4.1.0 before 4.1.0.1 | NVD |
References
- https://spring.io/security/cve-2026-59272vendor-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.