dbcve.org
ActivemqApplication · Apache

CVE-2026-49157

HIGH · 8.8 CVSS v3.1 Published 2026-06-01
Fix available
A fix is available. Upgrade to 5.19.7 / 6.2.6 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Incorrect Default Permissions vulnerability in Apache ActiveMQ. This issue affects Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6. The default Jolokia authorization settings granted non-admin (low-privilege) web-login accounts access to Jolokia operations which allowed executing broker management operations meant for admins such as addQueue and removeQueue. Users are recommended to upgrade to version 6.2.6 or 5.19.7, 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

Apache ActiveMQ has Incorrect Default Permissions in its Jolokia authorization configuration. Low-privilege web login accounts can access admin-level Jolokia operations like addQueue and removeQueue, allowing unauthorized broker management operations.

MitigationUpgrade to Apache ActiveMQ 6.2.6 or 5.19.7 which fixes the default Jolokia authorization settings to properly restrict admin operations to admin users only.

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.7>= 6.0.0, < 6.2.6

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

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

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
    Check the version file in the ActiveMQ installation directory, typically found in a version.properties or manifest file, or run 'activemq --version' if the command is available
    Affected if The installed version is less than 5.19.7, or is 6.0.0 through 6.2.5 (inclusive)
  2. Confirm Jolokia API is accessible
    Test connectivity to the Jolokia endpoint on the ActiveMQ web server, typically at /api/jolokia or /jolokia/ path
    Affected if The Jolokia API endpoint responds and is reachable over the network
  3. Locate Jolokia security configuration
    Find the Jolokia configuration file in the conf directory of the ActiveMQ installation, commonly named jolokia-access.xml or referenced in jetty.xml
    Affected if A Jolokia authorization configuration file exists and is being loaded by the broker
  4. Inspect role assignments for Jolokia operations
    Examine the Jolokia security policy file to identify which roles are permitted to execute operations, specifically looking for addQueue and removeQueue method permissions
    Affected if The configuration grants any role other than admin or administrator roles permission to execute broker management operations like addQueue or removeQueue

The environment is affected if the installed ActiveMQ version falls within the vulnerable range AND the Jolokia API is exposed with default authorization that permits non-admin users to execute privileged broker operations.

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.7 / 6.2.6 or later
Fixed in 5.19.76.2.6
Interim mitigation

Upgrade to Apache ActiveMQ 6.2.6 or 5.19.7 which fixes the default Jolokia authorization settings to properly restrict admin operations to admin users only.

Recommended fix High confidence

5.19.7 or 6.2.6 (depending on your current branch)

  1. Back up existing ActiveMQ configuration and data directories before upgrading
  2. Stop the current ActiveMQ instance
  3. Download Apache ActiveMQ version 5.19.7 (for 5.x branch) or 6.2.6 (for 6.x branch) from the official Apache repository
  4. Extract the new version to your target installation directory
  5. Restore your configuration from the backup (or review and adapt config files for any breaking changes)
  6. Start the upgraded ActiveMQ instance
  7. Verify that Jolokia web access works correctly and that non-admin users can no longer access admin-only Jolokia operations like addQueue and removeQueue

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

Fix this in Activemq Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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