Remote JVM termination: nested-array Java deserialization bypasses allowlist, triggers StackOverflowError, default JavaLangErrorHandler calls System.exit(99) (CVE-2026-59275) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-59275

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

Answer in brief

CVE-2026-59275 records a Unknown severity vulnerability in Remote JVM termination: nested-array Java deserialization bypasses allowlist, triggers StackOverflowError, default JavaLangErrorHandler calls System.exit(99). The current sources do not mark it as known exploited. The current feed maps Spring/Spring AMQP (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 27, 2026Updated Aug 27, 2026Source checked Aug 27, 2026First seen by HOL Aug 27, 2026Material review Aug 27, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Spring/Spring AMQP (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Spring/Spring AMQPgeneric	4.1.0 \|\| 4.0.0 \|\| 3.2.0 \|\| 0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Spring/Spring AMQP.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 27, 2026

Sources and claim methodology

Source referencespring.io

Upstream source 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

Quoted source text, attributed separately from HOL analysis.