SB20261120221 - Multiple vulnerabilities in Spring AMQP
Published: November 20, 2026
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 3 vulnerabilities.
1) Missing Release of Resource after Effective Lifetime (CVE-ID: CVE-2026-59403)
CWE-ID: CWE-772 - Missing Release of Resource after Effective Lifetime
CVSSv4: 7.1 [CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N]
The vulnerability allows a remote user to cause a denial of service by exhausting the AMQP session's link handles.
The vulnerability exists due to a failure to close AMQP 1.0 sender links in the Spring AMQP listener reply handler when sending replies. A remote user can trigger the listener's reply handling to exhaust the session's link handles and prevent further replies or link creation on the shared connection.
Only listener endpoints whose handler methods return a non-void result are affected.
2) Uncontrolled Recursion (CVE-ID: CVE-2026-59404)
CWE-ID: CWE-674 - Uncontrolled Recursion
CVSSv4: 7.1 [CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N]
The vulnerability allows a remote user to cause a denial of service in Spring AMQP message consumers.
The vulnerability exists due to unbounded recursion in DefaultMessagePropertiesConverter when converting AMQP message headers. A remote user can trigger stack exhaustion during message conversion to disrupt message consumption.
A listener container can enter a crash loop if the broker redelivers the unacknowledged message.
3) Acceptance of Extraneous Untrusted Data With Trusted Data (CVE-ID: CVE-2026-59395)
CWE-ID: CWE-349 - Acceptance of Extraneous Untrusted Data With Trusted Data
CVSSv4: 2.3 [CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a remote user to spoof trusted message metadata and potentially influence authorization or routing decisions.
The vulnerability exists due to acceptance of untrusted data alongside trusted data in SimpleAmqpHeaderMapper.toHeaders() when mapping incoming AMQP message headers. A remote user can supply publisher-controlled metadata that the mapper treats as framework-derived metadata, potentially causing a listener to make decisions based on untrusted values.
Remediation
Install update from vendor's website.