Unauthenticated data compromise and service interruption via deserialization
Published Aug 27, 2026 · Updated Aug 27, 2026
Unsafe deserialization in Spring Batch 5.2.6 and earlier and 6.0.0 through 6.0.4 allows remote attackers to expose or alter data or interrupt service. DefaultExecutionContextSerializer Base64-decodes a stored execution context and passes the bytes to ObjectInputStream.readObject() without a class allowlist. The vulnerable path is limited to the default JDBC job repository, but Spring has not published how remote attackers place crafted bytes in an execution context.
Summary
What happened
Unsafe deserialization in Spring Batch 5.2.6 and earlier and 6.0.0 through 6.0.4 allows remote attackers to expose or alter data or interrupt service. DefaultExecutionContextSerializer Base64-decodes a stored execution context and passes the bytes to ObjectInputStream.readObject() without a class allowlist. The vulnerable path is limited to the default JDBC job repository, but Spring has not published how remote attackers place crafted bytes in an execution context.
The record
- CVE
- CVE-2026-47878
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- Spring
- Product
- Spring Batch
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=5.2.6
- Affected versionversion=6.0.0 <=6.0.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo