Apache ActiveMQ Artemis: Address routing-type can be updated by user without the createAddress permission
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2025-27427
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 03:38 UTC · Revision 1
Source evidence
Apache ActiveMQ Artemis: Address routing-type can be updated by user without the createAddress permission
core-osv · Original sourcePublished 1 Apr 2025, 07:26 UTC
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.
osv:CVE-2025-27427
Complete source record
{
"id": "d6e6634b70223c8b604edffc239186affd0497f221811f05146f787a6259e59a",
"url": "https://osv.dev/vulnerability/CVE-2025-27427",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Apache ActiveMQ Artemis: Address routing-type can be updated by user without the createAddress permission",
"summary": "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.",
"evidence": "osv:CVE-2025-27427",
"products": [],
"severity": "low",
"structured": {
"id": "CVE-2025-27427",
"aliases": [
"CVE-2025-27427",
"GHSA-3w85-5p9g-h334"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/apache/artemis",
"type": "GIT",
"events": [
{
"introduced": "70e319d6e3fbdd8e882d3f791a97050672af8a5a"
},
{
"fixed": "2c3903ff71de7ecc6830d5f051dfc94d6df9b187"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:apache:artemis:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "2.0.0"
},
{
"fixed": "2.40.0"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"2.39.0",
"2.38.0",
"2.37.0",
"2.36.0",
"2.35.0",
"2.34.0",
"2.33.0",
"2.32.0",
"2.31.2",
"2.31.1",
"2.31.0",
"2.30.0",
"2.29.0",
"2.28.0",
"2.27.0",
"2.26.0",
"2.25.0",
"2.24.0",
"2.23.0",
"2.22.0",
"2.21.0",
"2.19.0",
"2.20.0",
"2.18.0",
"2.17.0",
"2.16.0",
"2.15.0",
"2.14.0",
"2.13.0",
"2.12.0",
"2.11.0",
"2.10.1",
"2.10.0",
"2.9.0",
"2.8.1",
"2.8.0",
"2.7.0",
"2.6.0",
"2.5.0",
"2.4.0",
"2.3.0",
"2.2.0",
"2.1.0",
"2.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-27427.json"
}
}
],
"modified": "2026-10-28T02:30:53.195259775Z",
"provider": "osv",
"references": [
"https://repo.maven.apache.org/maven2",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/27xxx/CVE-2025-27427.json",
"https://lists.apache.org/thread/8dzlm2vkqphyrnkrby8r8kzndsm5o6x8",
"https://nvd.nist.gov/vuln/detail/CVE-2025-27427"
],
"provider_metadata": {
"cwe_ids": [
"CWE-863"
],
"cna_assigner": "apache",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "2.0.0"
},
{
"last_affected": "2.39.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/27xxx/CVE-2025-27427.json"
}
},
"related_cves": [
{
"value": "CVE-2025-27427",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 522275,
"published_at": "2025-04-01T07:26:59.994+00:00"
}