ActiveMQ_CVE-2015-5254

ActiveMQ デシリアライゼーション CVE-2015-5254 脆弱性の説明：Apache ActiveMQ 5.13.0 より前の 5.x バージョンに安全上の脆弱性が存在します。この脆弱性は、プログラムがブローカーでシリアライズ可能なクラスを制限していないことに起因します。リモートの攻撃者は、特別に細工されたシリアライズ化された Java Message Service JMS ObjectMessage オブジェクトを利用して、任意のコードを実行する可能性があります。 影響を受けるバージョン：Apache ActiveMQ 5.13.0 より前の 5.x バージョン 0x01...

Exploitation-de-la-vuln-rabilit-CVE-2015-5254-

利用CVE-2015-5254漏洞 CVE-2015-5254漏洞是Apache ActiveMQ中的一个安全缺陷，ActiveMQ是一个广泛用于应用程序间通信的开源消息服务器。该漏洞影响ActiveMQ至5.13.0版本，其根源在于对发送的JMS ObjectMessage输入数据缺乏过滤。 网络扫描： nmap -p 61616 -Pn -T5 -n -sC -sV 172.17.0.1 通过其下载的docker文件夹启动ActiveMQ 2015： 我们检查ActiveMQ的版本： 它是5.11.1版本 漏洞利用： 对于这个漏洞，我们将使用以下命令： root@kitploit:...

CLEANSTART-2026-TK74523 Apache CXF's JMS transport deserializes the body of any inbound JMS ObjectMessage using native Java deserialization, with no type restrictions in place

Security vulnerability affects the wildfly package. Apache CXF's JMS transport deserializes the body of any inbound JMS ObjectMessage using native Java deserialization, with no type restrictions in place...

CVE-2026-40860

camel-jms JMS ObjectMessage 不安全反序列化复现工具 CVE-2026-40860 本项目演示了 Apache Camel 的 camel-jms 组件中存在的 Java 反序列化漏洞 （并间接影响 camel-sjms、camel-sjms2、camel-amqp、camel-activemq、camel-activemq6），该漏洞被跟踪为 CVE-2026-40860 。JmsBinding.extractBodyFromJms 方法在处理传入的 JMS ObjectMessage 时，通过 ObjectMessage.getObject...

CVE-2026-43866

camel-jms 伪造 DefaultExchangeHolder 过滤器绕过复现工具 CVE-2026-43866 本项目演示了 CVE-2026-43866 ，这是对 Apache Camel 的 camel-jms（以及 camel-sjms / JMS 系列）组件中 CVE-2026-40860 修复的一种绕过 。CVE-2026-40860 为传入的 JMS ObjectMessage 负载添加了反序列化后的类白名单（java.;javax.;org.apache.camel.;!）。但是...

Deserialization Of Untrusted Data

Apache CXF is vulnerable to Deserialization of Untrusted Data. The vulnerability is due to native Java deserialization of inbound JMS ObjectMessage objects without type restrictions, which allows an attacker who can place messages on the JMS destination to submit malicious serialized objects that...

CVE-2026-86404

EAP's Artemis deserialization configuration permits deserialization by default. ObjectMessage.getObject uses ObjectInputStreamWithClassLoader, which implements allow-list/block-list filtering via its checkSecurity/isTrustedType method. However, by default both allow-list and block-list are empty...

CVE-2026-86404 Artemis-server: artemis-jms-client: artemis-core-client: undertow-core: wildfly-messaging-activemq-subsystem: artemis messaging handlers in red hat eap permit deserialization by default

EAP's Artemis deserialization configuration permits deserialization by default. ObjectMessage.getObject uses ObjectInputStreamWithClassLoader, which implements allow-list/block-list filtering via its checkSecurity/isTrustedType method. However, by default both allow-list and block-list are empty...

CVE-2026-86404 Artemis-server: artemis-jms-client: artemis-core-client: undertow-core: wildfly-messaging-activemq-subsystem: artemis messaging handlers in red hat eap permit deserialization by default

EAP's Artemis deserialization configuration permits deserialization by default. ObjectMessage.getObject uses ObjectInputStreamWithClassLoader, which implements allow-list/block-list filtering via its checkSecurity/isTrustedType method. However, by default both allow-list and block-list are empty...

EUVD-2026-72352

EAP's Artemis deserialization configuration permits deserialization by default. ObjectMessage.getObject uses ObjectInputStreamWithClassLoader, which implements allow-list/block-list filtering via its checkSecurity/isTrustedType method. However, by default both allow-list and block-list are empty...

CVE-2026-86404

EAP's Artemis deserialization configuration permits deserialization by default. ObjectMessage.getObject uses ObjectInputStreamWithClassLoader, which implements allow-list/block-list filtering via its checkSecurity/isTrustedType method. However, by default both allow-list and block-list are empty...

PT-2026-86687

🚨HIGH - Red Hat EAP Artemis ObjectMessage Unsafe Deserialization Default CVE-2026-86404 In Red Hat EAP’s Artemis messaging, the deserialization trust check allows any class when both allow-list and block-list are empty, so untrusted ObjectMessage payloads deserialize by default. Remote attackers...

CVE-2026-66909

A flaw was found in Apache CXF. The Java Message Service JMS transport component improperly deserializes inbound JMS ObjectMessages without type restrictions. A remote attacker can exploit this by sending a specially crafted message to the service's JMS destination. This vulnerability could lead ...

camel-jms: Apache Camel JMS components: Arbitrary Exchange state injection

A flaw was found in Apache Camel JMS components. A remote attacker can exploit a deserialization vulnerability by sending a specially crafted ObjectMessage to a queue or topic consumed by an affected Camel application. This bypasses existing security checks, allowing the attacker to inject...

artemis-server: artemis-jms-client: artemis-core-client: undertow-core: wildfly-messaging-activemq-subsystem: artemis messaging handlers in Red Hat EAP permit deserialization by default

EAP's Artemis deserialization configuration permits deserialization by default. ObjectMessage.getObject uses ObjectInputStreamWithClassLoader, which implements allow-list/block-list filtering via its checkSecurity/isTrustedType method. However, by default both allow-list and block-list are empty...

artemis-server: artemis-jms-client: artemis-core-client: undertow-core: wildfly-messaging-activemq-subsystem: artemis messaging handlers in Red Hat EAP permit deserialization by default

EAP's Artemis deserialization configuration permits deserialization by default. ObjectMessage.getObject uses ObjectInputStreamWithClassLoader, which implements allow-list/block-list filtering via its checkSecurity/isTrustedType method. However, by default both allow-list and block-list are empty...

Deserialization of Untrusted Data

Overview Affected versions of this package are vulnerable to Deserialization of Untrusted Data in the deserialization process of inbound JMS ObjectMessage using native Java deserialization without type restrictions. An attacker can execute arbitrary code or cause a denial of service by submitting...

CVE-2026-66909 Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage

Apache CXF's JMS transport deserializes the body of any inbound JMS ObjectMessage using native Java deserialization, with no type restrictions in place. Any attacker able to place a message on the service's JMS destination can submit a malicious serialized object, leading to denial of service or,...

CVE-2026-43866

A flaw was found in Apache Camel JMS components. A remote attacker can exploit a deserialization vulnerability by sending a specially crafted ObjectMessage to a queue or topic consumed by an affected Camel application. This bypasses existing security checks, allowing the attacker to inject...

GHSA-F755-XP6R-8Q84 Apache Camel JMS deserialization filter bypass

Deserialization of Untrusted Data vulnerability in Apache Camel, Apache Camel JMS component. JmsBinding.extractBodyFromJms in camel-jms - and the equivalent JmsBinding in camel-sjms - deserializes the payload of an incoming JMS ObjectMessage via jakarta.jms.ObjectMessage.getObject whenever the...