CVE-2026-47856

JsonToObjectTransformer resolves the json__TypeId__ message header to an arbitrary class without an allow-list

Published Aug 26, 2026 CVSS 3.1 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
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

Analysis

AI-generated

Technical impact

Spring Integration's JsonToObjectTransformer determines the target class for JSON deserialization from a message header named json__TypeId__. The implementation uses ClassUtils.forName without restricting the classes that may be resolved. Based on the description, it is inferred that an attacker can supply a crafted header value that points to any class available on the application’s JVM, thereby triggering deserialization of malicious data. If the payload and the target class interact in a way that enables code execution, the vulnerability allows an attacker to run arbitrary code within the application’s process.

Affected Systems

The affected product is Spring Integration from the Spring vendor. Versions that are vulnerable include 5.5.21 and earlier, 6.4.0 through 6.4.12, 6.5.0 through 6.5.10, 7.0.0 through 7.0.5, and 7.1.0. Any deployment that incorporates one of these releases and exposes the JsonToObjectTransformer to untrusted input is at risk.

Risk and Exploitability

The CVSS score of 6.3 classifies the issue as medium severity. The EPSS score shows a very low exploitation probability (< 1 %). The vulnerability is not listed in CISA KEV. Based on the description, the likely attack vector is injection of a crafted json__TypeId__ header via network or internal messaging channels. Attackers can exploit the flaw by sending such a header, and no publicly known exploits are currently available. The absence of an allow‑list renders the condition effectively satisfied whenever the header is supplied.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Spring Integration to the latest available version (8.0.x or at least 7.1.1, 7.0.6, 6.5.11, 6.4.13, and newer 5.5.x releases) that removes the vulnerability.
  • If an upgrade is not feasible, configure the application to enforce an allow‑list for the json__TypeId__ header, restricting deserialization to known safe classes.
  • Restrict message traffic containing the json__TypeId__ header to authenticated and trusted sources, and consider disabling or sanitizing the header for external messages.

Generated by OpenCVE AI on August 28, 2026 at 07:57 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 Integration
CPEs cpe:2.3:a:vmware:spring_integration:*:*:*:*:*:*:*:*
Vendors & Products Vmware
Vmware spring Integration
Type Values Removed Values Added
Weaknesses CWE-20
CWE-415
Type Values Removed Values Added
Weaknesses CWE-502
Metrics ssvc

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

Type Values Removed Values Added
First Time appeared Spring
Spring spring Integration
Weaknesses CWE-20
CWE-415
Vendors & Products Spring
Spring spring Integration
Type Values Removed Values Added
Description 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
Title JsonToObjectTransformer resolves the json__TypeId__ message header to an arbitrary class without an allow-list
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Aug 27, 2026, 3:12 PM
Reserved
May 20, 2026, 10:00 AM
Status
Analyzed
Published
Aug 27, 2026, 1:17 AM
Modified
Sep 4, 2026, 8:09 PM