Spring AMQP CVE-2026-59275

Exploitation requires the attacker to hold authenticated publisher privileges on the AMQP broker sufficient to deliver a message to a queue consumed by an affected Spring AMQP listener (confirmed by PR:H in the CVSS vector). The network delivery vector (AV:N) means the message can be sent remotely, but high attack complexity (AC:H) indicates a specific message payload structure is required rather than a trivial or opportunistic attack. Limiting factors include: the attacker must have broker-authenticated write access, ruling out unauthenticated external attackers entirely; AC:H indicates reliable triggering requires specific knowledge of the vulnerable message format; and only applications running Spring AMQP 2.4.18 and earlier, 3.2.0-3.2.12, 4.0.0-4.0.4, or 4.1.0 are vulnerable. Standard deployments enforcing broker ACLs that restrict publishers to known internal identities substantially constrain the realistic attacker pool.

The NVD-assigned CVSS 3.1 score of 6.6 with vector AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H requires high attacker privileges and high attack complexity, substantially limiting real-world exploitability. However, the C:H and I:H impact metrics are inconsistent with the described vulnerability, which explicitly involves only availability loss through JVM termination - no confidentiality or integrity impact mechanism is described in available data. This scoring discrepancy is unresolved and should be verified against the vendor advisory at https://spring.io/security/cve-2026-59275. No EPSS score was provided in available intelligence, and no CISA KEV listing exists, indicating no confirmed mass exploitation at time of analysis. No public exploit code has been identified. Despite the moderate CVSS score, the operational consequence - abrupt, total JVM death with collateral damage to all co-located workloads - is significant in microservice or shared-process deployments. The PR:H requirement is the primary real-world risk limiter: an attacker must control an authenticated publisher identity on the AMQP broker, ruling out opportunistic external attacks.

An attacker who has obtained valid AMQP publisher credentials - through a compromised internal service account, overly permissive broker ACLs, or a malicious insider - crafts and delivers a specifically structured message to a queue actively consumed by an affected Spring AMQP listener. Upon processing, the listener invokes System.exit(99), immediately terminating the entire JVM and taking down all services co-located in that process with no graceful shutdown or recovery. No public exploit code demonstrating this technique has been identified at time of analysis.