CVE-2026-47856 json
JsonToObjectTransformer resolves the json__TypeId__ message header to an arbitrary class without an allow-list
published 2026-08-26 2 mo ago modified 2026-09-04 2 mo ago also EUVD-2026-66823
- cvss
- 6.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
Spring Integration's JSON to object conversion uses the json__TypeId__ header to choose the deserialization target type, and resolves that header value to a class with ClassUtils.forName and no type/package allow-list. Spring Integration 7.1.0 Spring Integration 7.0.0 - 7.0.5 Spring Integration 6.5.0 - 6.5.10 Spring Integration 6.4.0 - 6.4.12 Spring Integration 5.5.21 and earlier
Patch / fix
- vmware spring_integration 5.5.22, 6.4.13, 6.5.11, 7.0.5.1, 7.1.0.1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-47856 updated cvss 6.3
org.springframework.integration/spring-integration-core: Spring Integration: Arbitrary class resolution via `json__TypeId__` header
-
Red Hat Fuse 7 spring-integration-core 5.5.11affected: no fix planned “Out of support scope”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
Affected products
- Spring Spring Integration
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
spring.io
/security/cve-2026-47856
vendor-advisory
Sources
- CVE List CVE-2026-47856
- NVD CVE-2026-47856
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.