HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 39304 apache activemq client apache activemq broker
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Contribute to HOL
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 7.5CVE-2026-39304

Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Incorrect handling of TLSv1.3 KeyUpdate can be exploited to cause DoS via OOMCVE-2026-39304

Answer in brief

CVE-2026-39304 records a High severity (CVSS 7.5) vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Incorrect handling of TLSv1.3 KeyUpdate can be exploited to cause DoS via OOM. The current sources do not mark it as known exploited. The current feed maps Red Hat/activemq-all (generic), Red Hat/activemq-broker (generic), Red Hat/activemq-client (generic), Apache Software Foundation/Apache ActiveMQ (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Apr 10, 2026Updated Oct 26, 2026Source checked Nov 4, 2026First seen by HOL Jul 15, 2026Material review Oct 26, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 7.5
Exploitation
Not marked as known exploited
Affected software
13 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Red Hat/activemq-all (generic), Red Hat/activemq-broker (generic), Red Hat/activemq-client (generic), Apache Software Foundation/Apache ActiveMQ (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:a:apache:activemq:*:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:apache:activemq_broker:*:*:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Red Hat/activemq-allgeneric*Not reported
Red Hat/activemq-brokergeneric*Not reported
Red Hat/activemq-clientgeneric*Not reported
Apache Software Foundation/Apache ActiveMQgeneric>=0 <5.19.4 || >=6.0.0 <6.2.45.19.4, 6.2.4
Apache Software Foundation/Apache ActiveMQ Allgeneric>=0 <5.19.4 || >=6.0.0 <6.2.45.19.4, 6.2.4
Apache Software Foundation/Apache ActiveMQ Brokergeneric>=0 <5.19.4 || >=6.0.0 <6.2.45.19.4, 6.2.4
Apache Software Foundation/Apache ActiveMQ Clientgeneric>=0 <5.19.4 || >=6.0.0 <6.2.45.19.4, 6.2.4
Apache Software Foundation/org.apache.activemq:activemq-allgeneric>=0 <5.19.4 || >=6.0.0 <6.2.45.19.4, 6.2.4
Apache Software Foundation/org.apache.activemq:activemq-brokergeneric>=0 <5.19.4 || >=6.0.0 <6.2.45.19.4, 6.2.4
Apache Software Foundation/org.apache.activemq:activemq-clientgeneric>=0 <5.19.4 || >=6.0.0 <6.2.45.19.4, 6.2.4
Apache Software Foundation/org.apache.activemq:apache-activemqgeneric>=0 <5.19.4 || >=6.0.0 <6.2.45.19.4, 6.2.4

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Red Hat/activemq-all, Red Hat/activemq-broker, Red Hat/activemq-client.
  2. 2Review the reported fix. Update Apache Software Foundation/Apache ActiveMQ to 5.19.4; Apache Software Foundation/Apache ActiveMQ All to 5.19.4; Apache Software Foundation/Apache ActiveMQ Broker to 5.19.4; Apache Software Foundation/Apache ActiveMQ Client to 5.19.4; Apache Software Foundation/org.apache.activemq:activemq-all to 5.19.4; Apache Software Foundation/org.apache.activemq:activemq-broker to 5.19.4; Apache Software Foundation/org.apache.activemq:activemq-client to 5.19.4; Apache Software Foundation/org.apache.activemq:apache-activemq to 5.19.4 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Apr 10, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Oct 26, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Jul 15, 2026

Sources and claim methodology

  • Source referenceaccess.redhat.com
  • Source referenceactivemq.apache.org
  • Source referencebugzilla.redhat.com
  • Source referencesecurity.access.redhat.com
  • Source referenceopenwall.com
Upstream source description

Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ. ActiveMQ NIO SSL transports do not correctly handle TLSv1.3 handshake KeyUpdates triggered by clients. This makes it possible for a client to rapidly trigger updates which causes the broker to exhaust all its memory in the SSL engine leading to DoS. Note: TLS versions before TLSv1.3 (such as TLSv1.2) are broken but are not vulnerable to OOM. Previous TLS versions require a full handshake renegotiation which causes a connection to hang but not OOM. This is fixed as well. This issue affects Apache ActiveMQ Client: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ Broker: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ: before 5.19.4, from 6.0.0 before 6.2.4. Users are recommended to upgrade to version 6.2.4 or 5.19.5, which fixes the issue.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Apache ActiveMQ: LDAPAuthorizationMap allows authorization bypass via DN injectionSame apache software foundation/apache activemq package
  • Apache ZooKeeper: Denial of service through unbounded memory allocation in multiRead request handlingAlso CWE-770
  • Apache ZooKeeper: Unbounded recursion in snapshot serialization allows a client to render the server unrecoverableAlso CWE-770
  • Unbounded query cache growth from interpolated JSON paths and splice lists in EctoAlso CWE-770

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
CWE-400, CWE-770
Source
CVE List V5
Source checked
Nov 4, 2026
References
5 linked sources
Open source record