spring-amqp-deserialization

spring-amqp-deserialization Spring AMQP 反序列化漏洞 CVE-2023-34050 的概念验证 受影响的版本： 1.0.0 到 2.4.16 3.0.0 到 3.0.9 参考：https://spring.io/security/cve-2023-34050...

CVE-2016-2173

CVE-2016-2173 - Spring AMQP 中的远程代码执行 - 应用测试 描述 类 org.springframework.core.serializer.DefaultDeserializer 不会根据白名单验证反序列化的对象。通过提供精心编制的序列化对象（如 Chris Frohoff 的 Commons Collection gadget），可以实现远程代码执行。 受影响版本 1.0.0 至 1.5.4 供应商 Pivotal 的 Spring 安装 root@kitploit: - Maven 3.x+ - Java 1.7+ - RabbitMQ 运行应用漏洞...

CLSA-2026-1789371263 TuxCare security update for org.springframework.amqp (3 CVEs)

TuxCare rebuilt 7 org.springframework.amqp packages to address 3 CVEs. Fixed in 3.2.12-tuxcare.1...

Linux Distros Unpatched Vulnerability : CVE-2026-59272

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is exposed to man-in-the-middle interception of...

CVE-2026-59320

When a container-level ErrorHandler is configured the mitigation for finding 221000, each delivery whose processing throws still permanently consumes one link credit. After initialCredits default 100 failing messages the receiver's credit reaches zero and the broker stops delivering, leaving the...

CVE-2026-59320

CVE-2026-59320 affects Spring AMQP 4.1.0 . When a container-level ErrorHandler is configured, each delivery whose message processing throws an exception permanently consumes one link credit without replenishing it. After the receiver exhausts its initialCredits (default 100 ), the broker stops de...

CVE-2026-59320 In Spring AMQP the link credit never replenished on listener exception path

When a container-level ErrorHandler is configured the mitigation for finding 221000, each delivery whose processing throws still permanently consumes one link credit. After initialCredits default 100 failing messages the receiver's credit reaches zero and the broker stops delivering, leaving the...

EUVD-2026-67201

When a container-level ErrorHandler is configured the mitigation for finding 221000, each delivery whose processing throws still permanently consumes one link credit. After initialCredits default 100 failing messages the receiver's credit reaches zero and the broker stops delivering, leaving the...

CVE-2026-59272

Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is exposed to man-in-the-middle interception of every log event. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier...

EUVD-2026-67093

Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is exposed to man-in-the-middle interception of every log event. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier...

CVE-2026-59272

Spring AMQP 's Log4j2 AmqpAppender disables TLS hostname verification by default . Any application using this appender to ship logs to RabbitMQ over TLS, while relying on the documented default, is exposed to man-in-the-middle interception of every log event. The vulnerability is rated MEDIUM (CV...

CVE-2026-59272 Log4j2 AmqpAppender disables TLS hostname verification by default

Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is exposed to man-in-the-middle interception of every log event. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier...

CVE-2026-59275

A single hostile AMQP message can terminate the entire consumer JVM System.exit99, not just the listener thread — full availability loss for every workload co-located in that process. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier...

CVE-2026-59271

When the RabbitMQ management aliveness check fails, the configured admin password is embedded in cleartext in the thrown exception message. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier...

CVE-2026-59275

Spring AMQP versions 4.1.0, 4.0.0–4.0.4, 3.2.0–3.2.12, and 2.4.18 and earlier are affected by a remote JVM termination vulnerability. A single hostile AMQP message triggers nested-array Java deserialization that bypasses the allowlist, causing a StackOverflowError . The default JavaLangErrorHandl...

EUVD-2026-66849

A single hostile AMQP message can terminate the entire consumer JVM System.exit99, not just the listener thread — full availability loss for every workload co-located in that process. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier...

CVE-2026-59275 Remote JVM termination: nested-array Java deserialization bypasses allowlist, triggers StackOverflowError, default JavaLangErrorHandler calls System.exit(99)

A single hostile AMQP message can terminate the entire consumer JVM System.exit99, not just the listener thread — full availability loss for every workload co-located in that process. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier...

CVE-2026-59271 Admin password disclosed in BrokerNotAliveException message

When the RabbitMQ management aliveness check fails, the configured admin password is embedded in cleartext in the thrown exception message. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier...

EUVD-2026-66847

When the RabbitMQ management aliveness check fails, the configured admin password is embedded in cleartext in the thrown exception message. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier...

CVE-2026-59271

Spring AMQP (versions 2.4.18 and earlier, 3.2.0–3.2.12, 4.0.0–4.0.4, and 4.1.0) is affected by an information disclosure vulnerability. When the RabbitMQ management aliveness check fails, the configured admin password is embedded in cleartext within the BrokerNotAliveException message, potentiall...