Forged responses accepted over the XMPP client transport due to missing sender verification

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

Description

The client-side XMPP transport (XmppSenderConnection) accepts any incoming message stanza whose type and thread match the outbound request, without checking which JID sent it. Since the thread identifier travels in cleartext, an attacker able to observe or inject stanzas on the XMPP connection can send a forged response that the client accepts as the legitimate reply.

This issue only affects deployments where all the following are true:

  • The client uses the XmppMessageSender transport for request/response calls.
  • An attacker can observe the thread identifier of a request, for example through a federated server on the message's path, another client on the same account with message carbons enabled, or archive access.
  • That attacker can then deliver a stanza with a matching thread to the client's JID.

Affected Spring Products and Versions

Spring Web Services:

  • 5.0.0 - 5.0.3
  • 4.1.0 - 4.1.4
  • 4.0.0 - 4.0.19
  • 3.1.9 and earlier

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.
Fix versionAvailability
5.0.3.1Enterprise Support Only
5.0.4OSS
4.1.5Enterprise Support Only
4.0.20Enterprise Support Only
3.1.10Enterprise Support Only

No further mitigation steps are necessary.

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