Apache ActiveMQ Artemis User Without Create Address Permissions can Modify Address Routing-Type

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X · score source

EPSS

• CVE-2025-27427: 0.65% estimated exploitation activity in the next 30 days; percentile 51.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability exists in Apache ActiveMQ Artemis whereby a user with the createDurableQueue or createNonDurableQueue permission on an address can augment the routing-type supported by that address even if said user doesn't have the createAddress permission for that particular address. When combined with the send permission and automatic queue creation a user could successfully send a message with a routing-type not supported by the address when that message should actually be rejected on the basis that the user doesn't have permission to change the routing-type of the address. This issue affects Apache ActiveMQ Artemis from 2.0.0 through 2.39.0. Users are recommended to upgrade to version 2.40.0 which fixes the issue.

Published by the source

1 Apr 2025, 09:30 UTC

Last modified by the source

15 Jul 2025, 00:27 UTC

Source last checked

26 Oct 2026, 16:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3w85-5p9g-h334

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-27427

Advisory: Apache ActiveMQ Artemis User Without Create Address Permissions can Modify Address Routing-Type
IDs: CVE-2025-27427, GHSA-3w85-5p9g-h334
Record: https://patchnext.com/advisories/cve-2025-27427 (revision 1, source checked 26 Oct 2026, 16:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.activemq:artemis-server 2.40.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.activemq:artemis-server: affected >= 2.0.0, < 2.40.0; fixed in 2.40.0

## Suggested inspection (read-only)
- Maven org.apache.activemq:artemis-server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.activemq:artemis-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3w85-5p9g-h334 (GitHub-reviewed advisory GHSA-3w85-5p9g-h334 lists affected ranges: Maven org.apache.activemq:artemis-server >=2.0.0 <2.40.0)

Commands are suggestions: review each one before running it.