Skip to content
Noroxi
NVD / CVE Program· CNA apache

CVE-2026-33227: Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ Web, Apache ActiveMQ: Improper Limitation of a Pathname to a Restricted Cla

Noroxi assessment

Priority: Monitor (action score 17/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Apache Software Foundation Apache ActiveMQ 5.19.3, 6.2.2; Apache Software Foundation Apache ActiveMQ All 5.19.3, 6.2.2; Apache Software Foundation Apache ActiveMQ Broker 5.19.3, 6.2.2.

Low priority for now. Upgrade to Apache Software Foundation Apache ActiveMQ 5.19.3, 6.2.2; Apache Software Foundation Apache ActiveMQ All 5.19.3, 6.2.2; Apache Software Foundation Apache ActiveMQ Broker 5.19.3, 6.2.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Improper validation and restriction of a classpath path name vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ Web, Apache ActiveMQ. In two instances (when creating a Stomp consumer and also browsing messages in the Web console) an authenticated user provided "key" value could be constructed to traverse the classpath due to path concatenation. As a result, the application is exposed to a classpath path resource loading vulnerability that could potentially be chained together with another attack to lead to exploit. This issue affects Apache ActiveMQ Client: before 5.19.3, from 6.0.0 before 6.2.2; Apache ActiveMQ Broker: before 5.19.3, from 6.0.0 before 6.2.2; Apache ActiveMQ All: before 5.19.3, from 6.0.0 before 6.2.2; Apache ActiveMQ Web: before 5.19.3, from 6.0.0 before 6.2.2; Apache ActiveMQ: before 5.19.3, from 6.0.0 before 6.2.2. Users are recommended to upgrade to version 5.19.4 or 6.2.3, which fixes the issue. Note: 5.19.3 and 6.2.2 also fix this issue, but that is limited to non-Windows environments due to a path separator resolution bug fixed in 5.19.4 and 6.2.3.

MediumCVSS 4.3 · v3.1—No exploit Fix available
Published
Apr 7, 2026
Updated
Oct 26, 2026
EPSS
0.4% · 36th percentile

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-33227

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
apacheactivemq
apacheactivemq broker
apacheactivemq web

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache activemqbefore 5.19.3
  • apache activemq6.0.0 and later · before 6.2.2
  • apache activemq brokerbefore 5.19.3
  • apache activemq broker6.0.0 and later · before 6.2.2
  • apache activemq webbefore 5.19.3
  • apache activemq web6.0.0 and later · before 6.2.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache ActiveMQ

    • before 5.19.3affected · semver
    • 6.0.0 and later · before 6.2.2affected · semver
  • Apache Software Foundation Apache ActiveMQ All

    • before 5.19.3affected · semver
    • 6.0.0 and later · before 6.2.2affected · semver
  • Apache Software Foundation Apache ActiveMQ Broker

    • before 5.19.3affected · semver
    • 6.0.0 and later · before 6.2.2affected · semver
  • Apache Software Foundation Apache ActiveMQ Client

    • before 5.19.3affected · semver
    • 6.0.0 and later · before 6.2.2affected · semver
  • Apache Software Foundation Apache ActiveMQ Web

    • before 5.19.3affected · semver
    • 6.0.0 and later · before 6.2.2affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12activemqfrom 0—
Mavenorg.apache.activemq:activemq-allfrom 6.0.0 · before 6.2.26.2.2
Mavenorg.apache.activemq:activemq-allbefore 5.19.35.19.3
Mavenorg.apache.activemq:activemq-brokerfrom 6.0.0 · before 6.2.26.2.2
Mavenorg.apache.activemq:activemq-brokerbefore 5.19.35.19.3
Mavenorg.apache.activemq:activemq-clientfrom 6.0.0 · before 6.2.26.2.2
Mavenorg.apache.activemq:activemq-clientbefore 5.19.35.19.3
Mavenorg.apache.activemq:activemq-webfrom 6.0.0 · before 6.2.26.2.2
Mavenorg.apache.activemq:activemq-webbefore 5.19.35.19.3

Other highest-scoring records for the same primary product.

  • CVE-2023-46604Apache ActiveMQ, Apache ActiveMQ Legacy OpenWire Module: Unbounded deserialization causes ActiveMQ to be vulnerable to a remote code execution (RCE) attackKEV
    99Now
  • CVE-2016-3088The Fileserver web application in Apache ActiveMQ 5.x before 5.14.0 allows remote attackers to upload and execute arbitrary files via an HTTKEV
    99Now
  • CVE-2026-34197Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Authenticated users could perform RCE via Jolokia MBeansKEV
    94Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-27533May 7, 2025 · Apache ActiveMQ: Unchecked buffer length can cause excessive memory allocation
    30Monitor
  • ← EarlierCVE-2025-66168Mar 4, 2026 · Apache ActiveMQ, Apache ActiveMQ All Module, Apache ActiveMQ MQTT Module: MQTT control packet remaining length field is not properly validated
    35Monitor
  • Later →CVE-2026-39304Apr 10, 2026 · Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Incorrect handling of TLSv1.3 KeyUpdate can be exploited to cause DoS via
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Apache Software Foundation Apache ActiveMQ5.19.3Vendor (CNA)
Apache Software Foundation Apache ActiveMQ6.2.2Vendor (CNA)
Apache Software Foundation Apache ActiveMQ All5.19.3Vendor (CNA)
Apache Software Foundation Apache ActiveMQ All6.2.2Vendor (CNA)
Apache Software Foundation Apache ActiveMQ Broker5.19.3Vendor (CNA)
Apache Software Foundation Apache ActiveMQ Broker6.2.2Vendor (CNA)
Apache Software Foundation Apache ActiveMQ Client5.19.3Vendor (CNA)
Apache Software Foundation Apache ActiveMQ Client6.2.2Vendor (CNA)
Apache Software Foundation Apache ActiveMQ Web5.19.3Vendor (CNA)
Apache Software Foundation Apache ActiveMQ Web6.2.2Vendor (CNA)
Maven:org.apache.activemq:activemq-all5.19.3Package registry (OSV)
Maven:org.apache.activemq:activemq-all6.2.2Package registry (OSV)
Maven:org.apache.activemq:activemq-broker5.19.3Package registry (OSV)
Maven:org.apache.activemq:activemq-broker6.2.2Package registry (OSV)
Maven:org.apache.activemq:activemq-client5.19.3Package registry (OSV)
Maven:org.apache.activemq:activemq-client6.2.2Package registry (OSV)
Maven:org.apache.activemq:activemq-web5.19.3Package registry (OSV)
Maven:org.apache.activemq:activemq-web6.2.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records