Spring AMQP Publisher-Controlled Headers Overwrite Framework-Derived amqp_* Headers

MEDIUM | NOVEMBER 19, 2026 | CVE-2026-59395

Description

SimpleAmqpHeaderMapper.toHeaders() first populates the Spring Messaging headers with framework-derived values from the received MessageProperties (such as amqp_receivedUserId, amqp_consumerQueue, amqp_deliveryTag and amqp_redelivered) and then copies the raw AMQP message headers, which are fully controlled by the publisher. As a result, a publisher can supply custom headers whose names collide with the amqp_* constants and silently replace the trusted values that downstream @RabbitListener handlers see via @Header or MessageHeaders.

Applications are affected if an attacker is able to publish messages routed to a listener and the application relies on an amqp_* framework header, for example AmqpHeaders.RECEIVED_USER_ID (broker-validated identity) or AmqpHeaders.CONSUMER_QUEUE, for authorization or routing decisions.

Affected Spring Products and Versions

Spring AMQP:

  • 4.1.0 - 4.1.2
  • 4.0.0 - 4.0.6
  • 3.2.0 - 3.2.13
  • 2.4.19 and earlier

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.
Fix versionAvailability
4.1.2.1Enterprise Support Only
4.1.3OSS
4.0.6.1Enterprise Support Only
4.0.7OSS
3.2.14Enterprise Support Only
2.4.20Enterprise Support Only

Users of affected versions who cannot upgrade should obtain trusted values, such as the received user id or consumer queue, directly from the MessageProperties of the received org.springframework.amqp.core.Message rather than from the mapped amqp_* Spring Messaging headers.

History

  • 2026-11-19: Initial vulnerability report published.

Get ahead

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

Learn more

Get support

TrueSource Spring Enterprise 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