Vulnerability in activemq (CVE-2026-53916)
Summary
Vulnerability in activemq (CVE-2026-53916). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.19.8, 6.2.7 or later.
Original description
The description as published by the source.
Memory Allocation with Excessive Size Value vulnerability in Apache ActiveMQ, Apache ActiveMQ All, Apache ActiveMQ Stomp.
An unauthenticated client that opens a STOMP NIO connection can send header bytes that never terminate which makes the broker buffer them without limit, exhausting the JVM heap.
This issue affects Apache ActiveMQ: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ All: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ Stomp: before 5.19.8, from 6.0.0 before 6.2.7.
Users are recommended to upgrade to version 6.2.7 or 5.19.8, which fixes the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53916 has been found in activemq.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade activemq to 5.19.8, 6.2.7 or later.
If unsure, ask your IT team or search "activemq CVE-2026-53916" on the vendor's site.
CVE-2026-53916 (activemq) — CWE-789 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.19.8, 6.2.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-789) exists in activemq.
Check the vendor advisory for the affected versions of activemq.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 5.19.8, 6.2.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'activemq' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade activemq to 5.19.8, 6.2.7ステージング環境で 5.19.8, 6.2.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-53916 activemq
- Ubuntu UBUNTU-CVE-2026-53916 activemq
References
- advisory lists.apache.org
- advisory openwall.com
- web nvd.nist.gov
- web github.com