CVE-2026-59275

Remote JVM termination: nested-array Java deserialization bypasses allowlist, triggers StackOverflowError, default JavaLangErrorHandler calls System.exit(99)

Published Aug 27, 2026 CVSS 3.1 · 6.6 Medium EPSS < 1% KEV · Not listed
Description
A single hostile AMQP message can terminate the entire consumer JVM (System.exit(99)), not just the listener thread — full availability loss for every workload co-located in that process.
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

Analysis

AI-generated

Technical impact

A malicious AMQP message crafted with a nested array structure bypasses Spring AMQP's deserialization allowlist. The deserialization process overflows the stack, causing a StackOverflowError. The default JavaLangErrorHandler then invokes System.exit(99), terminating the entire JVM. This results in a complete loss of availability for the consumer and all other workloads running in the same process. The vulnerability is an instance of insecure deserialization, classified as CWE‑502.

Affected Systems

The affected software is Spring AMQP from the Spring framework. Vulnerable versions include Spring AMQP 4.1.0, 4.0.0 through 4.0.4, 3.2.0 through 3.2.12, and any release version 2.4.18 and earlier. All installations of these versions exposed to untrusted AMQP traffic are at risk.

Risk and Exploitability

The CVSS score of 6.6 rates this issue as moderate, but the exploitability can be high because it requires only a single crafted AMQP packet from an external party. EPSS is not available, and the vulnerability is not currently listed in the CISA KEV catalog. A likely attack vector is a remote AMQP client that can send messages to the consumer queue. Successful exploitation results in immediate process termination and a denial of service for the entire JVM, making timely remediation critical.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Spring AMQP 4.1.1 or newer.
  • Implement a custom Java error handler that suppresses System.exit calls during deserialization errors.
  • Restrict AMQP connections to trusted clients only, using broker authentication and network-level controls.
  • Set up a process supervisor to automatically restart the JVM if it exits unexpectedly.

Generated by OpenCVE AI on August 27, 2026 at 07:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
First Time appeared Vmware
Vmware spring Advanced Message Queuing Protocol
CPEs cpe:2.3:a:vmware:spring_advanced_message_queuing_protocol:*:*:*:*:*:*:*:*
Vendors & Products Vmware
Vmware spring Advanced Message Queuing Protocol
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Spring
Spring spring Amqp
Weaknesses CWE-502
Vendors & Products Spring
Spring spring Amqp
Type Values Removed Values Added
Description A single hostile AMQP message can terminate the entire consumer JVM (System.exit(99)), not just the listener thread — full availability loss for every workload co-located in that process. 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
Title Remote JVM termination: nested-array Java deserialization bypasses allowlist, triggers StackOverflowError, default JavaLangErrorHandler calls System.exit(99)
References
Metrics cvssV3_1

{'score': 6.6, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Aug 28, 2026, 3:55 AM
Reserved
Jul 4, 2026, 6:13 PM
Status
Analyzed
Published
Aug 27, 2026, 6:17 AM
Modified
Sep 1, 2026, 6:22 PM