Skip to main content
EPSS 0.3%top 83%

CVE-2026-59272: CWE-297 Improper Validation of Certificate with Host Mismatch in Spring Spring AMQP

0
Medium
VulnerabilityCVE-2026-59272cvecve-2026-59272cwe-297
Published: 08/27/2026 (08/27/2026, 16:41:08 UTC)
Source: CVE Database V5
Vendor/Project: Spring
Product: Spring AMQP

Description

CVE-2026-59272 is a vulnerability in Spring AMQP affecting versions 2.4.18 and earlier, 3.2.0 through 3.2.12, 4.0.0 through 4.0.4, and 4.1.0. It involves improper validation of TLS certificates with host mismatches when applications send logs to RabbitMQ over TLS using the Log4j2 appender with default settings. This flaw can allow man-in-the-middle interception of log events.

CVSS v3.1

Score 6.8medium

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected software

Spring

Spring AMQP

Affected versions
>=4.0.0 <=4.0.4>=3.2.0 <=3.2.12>=0 <=2.4.18=4.1.0

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/10/2026, 04:53:10 UTC

Technical Analysis

This vulnerability (CWE-297) in Spring AMQP arises from improper validation of TLS certificates, specifically failing to verify that the certificate's hostname matches the intended RabbitMQ server. Applications shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on default configurations, are susceptible to man-in-the-middle attacks that intercept log data. The affected versions include 2.4.18 and earlier, 3.2.0 through 3.2.12, 4.0.0 through 4.0.4, and 4.1.0. No official remediation or patch is currently documented.

Potential Impact

Successful exploitation allows an attacker positioned as a man-in-the-middle to intercept every log event sent over TLS to RabbitMQ, potentially exposing sensitive log data. The vulnerability impacts confidentiality and integrity of log transmissions but does not affect availability.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider configuring TLS settings to enforce strict hostname verification or avoid relying on default Log4j2 appender settings that do not validate hostnames properly.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
vmware
Date Reserved
2026-07-04T18:13:09.972Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6a906bacacd9273b49839a7f

Added to database: 08/27/2026, 16:54:04 UTC

Last enriched: 09/10/2026, 04:53:10 UTC

Last updated: 10/10/2026, 06:48:18 UTC

Views: 46

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses