Spring Boot’s auto‑configuration for RabbitMQ allows an SSL bundle but fails to perform hostname verification, creating an improper certificate validation weakness (CWE‑295). This means a malicious broker or network attacker can impersonate the intended RabbitMQ broker, potentially intercepting or altering traffic between the Spring Boot application and the broker. The reported CVSS score of 5 indicates a moderate risk of data confidentiality and integrity compromise.

Spring Boot 4.0.0 through 4.0.5 and 3.5.0 through 3.5.13 are affected; the vulnerability is fixed in Spring Boot 4.0.6 and 3.5.14 respectively.

The vulnerability can be exploited when an application is configured to use an SSL bundle for RabbitMQ connections, typically over a network that could be monitored or controlled by an adversary. Since hostname verification is not performed, an attacker who can influence the broker endpoint can conduct a man‑in‑the‑middle attack. With a CVSS score of 5 and no EPSS data, exploitation likelihood is uncertain but the lack of KEV listing suggests no widespread active exploitation yet. The risk remains moderate and warrants timely remediation.