dbcve.org
ActivemqApplication · Apache

CVE-2026-52760

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 5.19.8 / 6.2.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache ActiveMQ, Apache ActiveMQ Web Console. The browse page in the web console renders a message Id directly without sanitization. This allows an authenticated producer to send a message with a JMS message ID that has been crafted to contain HTML/JavaScript such that when an administrator browses the queue in the Web Console, the payload executes in their browser. This issue affects Apache ActiveMQ: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ Web Console: 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stored XSS vulnerability in Apache ActiveMQ Web Console's browse page where JMS message IDs are rendered without sanitization. An authenticated producer can embed malicious HTML/JavaScript in a message ID that executes when an administrator views the queue through the web console.

MitigationUpgrade to Apache ActiveMQ version 5.19.8 or 6.2.7 which contains the fix for proper input sanitization of message IDs in the web console.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ActivemqApplication
Affected:< 5.19.8>= 6.0.0, < 6.2.7
Activemq WebApplication
Affected:< 5.19.8>= 6.0.0, < 6.2.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Apache ActiveMQ version
    Run 'activemq --version' or check the version file in the ActiveMQ installation directory (typically bin/activemq or lib/activemq-x.x.x.jar). Compare the version number against the affected ranges: < 5.19.8 or >= 6.0.0 but < 6.2.7.
    Affected if The installed version falls within < 5.19.8 or >= 6.0.0 to < 6.2.7.
  2. Confirm Web Console is enabled
    Check the conf/jetty.xml or conf/jetty-realm.properties file for web console configuration. Look for the 'webconsole' context path or port 8161 (default web console port) in the configuration.
    Affected if The web console is enabled and accessible on the default port or configured port.
  3. Verify browse page is accessible
    Attempt to access the queue browse page via HTTP: http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=*,destinationType=Queue,destinationName=* (or navigate to the web console browse page at /queueBrowse).
    Affected if The browse page is reachable without authentication or with admin credentials.
  4. Inspect message ID rendering in web console
    Review the JSP or Java source files in the web console module that handle message display, specifically files that render message IDs on the browse page (typically under webconsole/web/src/main/webapp or similar).
    Affected if The code does not perform HTML encoding/sanitization on message IDs before rendering.

You are affected if your ActiveMQ version is < 5.19.8 or >= 6.0.0 but < 6.2.7 AND the web console browse page is enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.19.8 / 6.2.7 or later
Fixed in 5.19.86.2.7
Interim mitigation

Upgrade to Apache ActiveMQ version 5.19.8 or 6.2.7 which contains the fix for proper input sanitization of message IDs in the web console.

Recommended fix High confidence

Apache ActiveMQ 6.2.7 (or 5.19.8 for 5.x line)

  1. Backup your current ActiveMQ configuration and data directories
  2. Stop the current ActiveMQ instance
  3. Download Apache ActiveMQ version 5.19.8 (for 5.x line) or 6.2.7 (recommended for both 5.x and 6.x lines) from the official Apache distribution site
  4. Extract the new version to your installation directory
  5. Migrate any custom configuration files from the backup to the new installation
  6. Start the upgraded ActiveMQ instance
  7. Verify the web console is accessible and the browse page properly sanitizes message IDs
Caveat Review release notes for any deprecated features or configuration changes between your current version and the target version; test in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Activemq Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-52760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-52760 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data