CVE-2026-47875: Spring Batch deserialization bypass in Jackson2ExecutionContextStringSerializer

CVE-2026-47875 · Severity: medium · CVSS 5.6 · Published 2026-08-27

Spring Batch is a widely-used framework for batch processing in Java applications. The vulnerability allows attackers to execute arbitrary code on systems using Spring Batch when processing untrusted job execution data. An attacker could leverage this to compromise applications and their underlying servers, potentially leading to data theft, service disruption, or complete system takeover.

Vendors: Spring.

Quick answers

Is CVE-2026-47875 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-47875 being exploited in the wild.
How severe is CVE-2026-47875?
Medium severity, with a CVSS score of 5.6, published 27 August 2026.
Which products and versions are affected?
Spring Batch 6.0.0-6.0.4, 5.2.0-5.2.6.
Is there a fix for CVE-2026-47875?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-47875 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-47875?
Check whether you run Spring Batch at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a deserialization attack affecting Jackson2ExecutionContextStringSerializer in Spring Batch. The JobParameterDeserializer fails to properly enforce a trusted-types allowlist, permitting an attacker to craft malicious serialized input that bypasses type restrictions. When an application deserializes execution contexts from an untrusted job repository source, an attacker can inject known Jackson RCE gadget chains to achieve arbitrary code execution. The attack requires an untrusted data source for the job repository but does not require prior authentication or user interaction.

Affected products

  • Spring Batch 6.0.0-6.0.4, 5.2.0-5.2.6

Timeline

  • 2026-08-27: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.