[KEV] Vulnerability in Apache activemq (CVE-2026-34197)
Summary
vulnerability in Apache activemq (CVE-2026-34197). Risk of unauthorized operations or information disclosure. Listed in CISA KEV — actively exploited.
Original description
The description as published by the source.
Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ.
Apache ActiveMQ Classic exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ on the web console. The default Jolokia access policy permits exec operations on all ActiveMQ MBeans (org.apache.activemq:*), including
BrokerService.addNetworkConnector(String) and BrokerService.addConnector(String).
An authenticated attacker can invoke these operations with a crafted discovery URI that triggers the VM transport's brokerConfig parameter to load a remote Spring XML application context using ResourceXmlApplicationContext.
Because Spring's ResourceXmlApplicationContext instantiates all singleton beans before the BrokerService validates the configuration, arbitrary code execution occurs on the broker's JVM through bean factory methods such as Runtime.exec().
This issue affects Apache ActiveMQ Broker: before 5.19.4, from 6.0.0 before 6.2.3; Apache ActiveMQ All: before 5.19.4, from 6.0.0 before 6.2.3; Apache ActiveMQ: before 5.19.4, from 6.0.0 before 6.2.3.
Users are recommended to upgrade to version 5.19.4 or 6.2.3, which fixes the issue
Source: CISA Known Exploited Vulnerabilities NVD GitHub Advisory CISA KEV
AI summary
Written by an external AI model and may contain mistakes. Check the original description and references below before acting on it.
An issue in Apache ActiveMQ involves improper input validation, allowing attackers to remotely execute code without authentication. This can lead to severe consequences, similar to past data breaches caused by similar flaws. Immediate remediation is essential.
Apache ActiveMQ contains a vulnerability due to improper input validation, leading to potential code injection. Attackers can execute code remotely via specific HTTP requests. The precise affected and fixed versions are not specified here but refer to the official advisory. A potential workaround includes applying restrictive ACLs to block unauthorized IPs. Immediate patching is recommended as remote exploits without authentication are possible.
Apache ActiveMQの入力値の検証不足により、コードインジェクションが可能です。
具体的なエンドポイントやパラメータは情報なし
高 (認証不要のリモート操作でコード実行可能)
公式アドバイザリを参照し、即時にパッチを適用
制限的なACLを適用し、未承認IPからのトラフィックをブロック
N/A
Related past incidents Similar incidents extracted from past CVEs
Similar improper input validation in Apache Struts leading to RCE.
Apache Log4j vulnerability allowing unauthorized RCE due to improper input handling.
Apache Tomcat vulnerability due to insufficient validation enabling remote code execution.
If this happens at your company Expected impact per business scenario
攻撃者が不正にコードを実行し、顧客情報を漏洩させる可能性がある。
攻撃者がリモートからシステム管理権限を取得し、情報の改ざんや漏洩を招く恐れがある。
誤ったコードがクラウドリソースを過剰に消費し、予期しないダウンタイムを引き起こす可能性がある。
脆弱性を悪用される前に、直ちにシステムをパッチし、制限的なアクセス制御リストを適用すること。
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'activemq' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
activemqを grep し、稼働しているサービス・バージョンを把握する。 -
4Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。Step 3 で兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-34197 activemq
- Ubuntu UBUNTU-CVE-2026-34197 activemq
References
- advisory NVD
- web activemq.apache.org
- web openwall.com
- web access.redhat.com
- web bugzilla.redhat.com
- web security.access.redhat.com
- web cisa.gov