dbcve.org
ActivemqApplication · Apache

CVE-2026-41043

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 5.19.6 / 6.2.5 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in Apache ActiveMQ, Apache ActiveMQ Web. An authenticated attacker can show malicious content when browsing queues in the web console by overriding the content type to be HTML (instead of XML) and by injecting HTML into a JMS selector field. This issue affects Apache ActiveMQ: before 5.19.6, from 6.0.0 before 6.2.5; Apache ActiveMQ Web: before 5.19.6, from 6.0.0 before 6.2.5. Users are recommended to upgrade to version 6.2.5 or 5.19.6, 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

This is a stored Cross-Site Scripting (XSS) vulnerability in Apache ActiveMQ's web console. An authenticated attacker can inject malicious HTML/JavaScript into a JMS selector field when browsing queues, then trick another user into viewing that content by overriding the content type from XML to HTML, causing the injected script to execute in the victim's browser.

MitigationUpgrade Apache ActiveMQ to version 5.19.6 or 6.2.5 or later, which includes proper input validation/sanitization for JMS selector fields 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.6>= 6.0.0, < 6.2.5
Activemq WebApplication
Affected:< 5.19.6>= 6.0.0, < 6.2.5

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 Apache ActiveMQ version
    Locate the ActiveMQ installation and check its version. This is typically found in release notes, a VERSION file, or displayed in the startup banner. Compare your installed version to the affected ranges: versions below 5.19.6, or versions 6.0.0 through 6.2.4.
    Affected if The installed version is below 5.19.6, or is 6.0.0 through 6.2.4
  2. Confirm web console is enabled
    Check if the ActiveMQ web console is enabled and accessible. This is typically configured in the Jetty configuration files (jetty.xml) or similar. Look for console port bindings, commonly port 8161.
    Affected if The web console is enabled and network-accessible
  3. Check if JMS selector feature is reachable
    Verify that the queue browsing functionality in the web console is accessible to users. This involves checking authentication settings and access controls for the console endpoint.
    Affected if The JMS selector field in queue browsing is accessible to authenticated users without additional restrictions
  4. Inspect content type handling
    Review configuration or code related to content type handling in the web console. The vulnerability involves overriding content type from XML to HTML to trigger XSS.
    Affected if Content type headers can be overridden by users to render data as HTML rather than the intended format

You are affected if your ActiveMQ version is in the vulnerable range and the web console with queue browsing and JMS selector fields is accessible to authenticated users.

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.6 / 6.2.5 or later
Fixed in 5.19.66.2.5
Interim mitigation

Upgrade Apache ActiveMQ to version 5.19.6 or 6.2.5 or later, which includes proper input validation/sanitization for JMS selector fields in the web console.

Recommended fix High confidence

5.19.6 or 6.2.5

  1. Backup your current ActiveMQ configuration and data directories
  2. Stop the running ActiveMQ service
  3. Download Apache ActiveMQ version 5.19.6 or 6.2.5 from the official Apache ActiveMQ distribution (activemq.apache.org)
  4. Extract the new version to your target installation directory
  5. Restore your configuration from the backup (copy conf/* files)
  6. Start the ActiveMQ service
  7. Log in to the web console and verify the queue browser functionality works correctly
  8. Confirm the fix by testing JMS selector fields with HTML content (should be properly escaped)
Caveat Review release notes for any configuration changes between your current version and the target upgrade version before deploying

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

Fix this in Activemq Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41043 — 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-41043 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