EmbeddedHeadersJsonMessageMapper default gives wire peer full control of MessageHeaders

MEDIUM | AUGUST 20, 2026 | CVE-2026-59322

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. As a result, any transport component using EmbeddedHeadersJsonMessageMapper with default settings—such as ZeroMqChannel when receiving raw socket bytes—allows external network peers to supply arbitrary MessageHeaders entries (including sensitive control headers like replyChannel, errorChannel, routingSlip, and json__TypeId__). These injected headers propagate directly into downstream internal components, such as BeanFactoryChannelResolver, through standard handler/error-handler pipelines.

Affected Spring Products and Versions

Spring Integration:

  • 7.1.0 - 7.1.0
  • 7.0.0 - 7.0.5
  • 6.5.0 - 6.5.10
  • 6.4.0 - 6.4.12
  • 5.5.21 and earlier

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.
Fix versionAvailability
7.1.0.1Enterprise Support Only
7.1.1OSS
7.0.5.1Enterprise Support Only
7.0.6OSS
6.5.11Enterprise Support Only
6.4.13Enterprise Support Only
5.5.22Enterprise Support Only

No further mitigation steps are necessary.

History

  • 2026-08-20: Initial vulnerability report published.

Get ahead

VMware offers training and certification to turbo-charge your progress.

Learn more

Get support

Tanzu Spring offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.

Learn more

Upcoming events

Check out all the upcoming events in the Spring community.

View all