CVE-2026-59322

EmbeddedHeadersJsonMessageMapper default gives wire peer full control of MessageHeaders

Published Aug 27, 2026 CVSS 3.1 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
The EmbeddedHeadersJsonMessageMapper defaults to an overly permissive header parsing posture in its constructor. When decodeNativeFormat processes raw byte payloads, it deserializes embedded JSON headers into a plain Map and constructs a GenericMessage with MutableMessageHeaders without sanitizing or filtering untrusted header names by default.
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

The EmbeddedHeadersJsonMessageMapper in Spring Integration defaults to a permissive header parsing mode. When raw byte payloads are decoded, the mapper deserializes embedded JSON headers into an unfiltered plain map and constructs a GenericMessage with mutable headers. Because untrusted header names are not sanitized or restricted, a remote party can inject arbitrary headers into the message. This can lead to unauthorized manipulation of message metadata, potentially affecting downstream processing and the behavior of the application that consumes the message.

Affected Systems

Spring Integration versions 5.5.21 and earlier, 6.4.0‑6.4.12, 6.5.0‑6.5.10, 7.0.0‑7.0.5, and 7.1.0 are affected. Systems using these versions and the default EmbeddedHeadersJsonMessageMapper configuration are susceptible to the flaw.

Risk and Exploitability

The CVSS score of 6.3 indicates moderate severity; EPSS is not available and the vulnerability is not listed in the CISA KEV catalog, suggesting that mass exploitation may be low. Based on the description, the likely attack vector is the delivery of a crafted message over the network that includes malicious JSON header data. An attacker exploiting this flaw can insert arbitrary headers and manipulate how the message is interpreted by the application, potentially leading to escalation of privileges or denial‑of‑service conditions if header handling is critical to the workflow.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Spring Integration to a fixed release that removes the default permissive header parsing posture (ensure the version is newer than 7.1.0, 7.0.5, 6.5.10, 6.4.12, or 5.5.21).
  • If an immediate upgrade is not possible, reconfigure EmbeddedHeadersJsonMessageMapper to enforce a strict header filter or whitelist by customizing the constructor parameters to sanitize or reject unwanted header names.
  • Monitor application logs for abnormal message headers or injection attempts, and apply runtime monitoring to detect any exploitation attempts early.

Generated by OpenCVE AI on August 28, 2026 at 06:43 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
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
Vendors & Products Spring
Spring spring Integration
Type Values Removed Values Added
Weaknesses CWE-20
Type Values Removed Values Added
Description The EmbeddedHeadersJsonMessageMapper defaults to an overly permissive header parsing posture in its constructor. When decodeNativeFormat processes raw byte payloads, it deserializes embedded JSON headers into a plain Map and constructs a GenericMessage with MutableMessageHeaders without sanitizing or filtering untrusted header names by default. 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 EmbeddedHeadersJsonMessageMapper default gives wire peer full control of MessageHeaders
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-20

    Improper Input Validation

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Aug 28, 2026, 10:46 PM
Reserved
Jul 4, 2026, 6:14 PM
Status
Analyzed
Published
Aug 27, 2026, 8:17 PM
Modified
Sep 1, 2026, 11:39 PM