UBUNTU-CVE-2026-27446 (CVE-2026-27446)
Vulnerability from osv_ubuntu – Published: 2026-03-04 09:15 – Updated: 2026-10-28 17:33 – Source websiteMissing Authentication for Critical Function (CWE-306) vulnerability in Apache Artemis, Apache ActiveMQ Artemis. An unauthenticated remote attacker can use the Core protocol to force a target broker to establish an outbound Core federation connection to an attacker-controlled rogue broker. This could potentially result in message injection into any queue and/or message exfiltration from any queue via the rogue broker. This impacts environments that allow both: - incoming Core protocol connections from untrusted sources to the broker - outgoing Core protocol connections from the broker to untrusted targets This issue affects: - Apache Artemis from 2.50.0 through 2.51.0 - Apache ActiveMQ Artemis from 2.11.0 through 2.44.0. Users are recommended to upgrade to Apache Artemis version 2.52.0, which fixes the issue. The issue can be mitigated by one of the following: - Remove Core protocol support from any acceptor receiving connections from untrusted sources. Incoming Core protocol connections are supported by default via the "artemis" acceptor listening on port 61616. See the "protocols" URL parameter configured for the acceptor. An acceptor URL without this parameter supports all protocols by default, including Core. - Use two-way SSL (i.e. certificate-based authentication) in order to force every client to present the proper SSL certificate when establishing a connection before any message protocol handshake is attempted. This will prevent unauthenticated exploitation of this vulnerability. - Implement and deploy a Core interceptor to deny all Core downstream federation connect packets. Such packets have a type of (int) -16 or (byte) 0xfffffff0. Documentation for interceptors is available at https://artemis.apache.org/components/artemis/documentation/latest/intercepting-operations.html .
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "activemq",
"binary_version": "5.13.2+dfsg-2ubuntu0.1~esm1"
},
{
"binary_name": "libactivemq-java",
"binary_version": "5.13.2+dfsg-2ubuntu0.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "activemq",
"purl": "pkg:deb/ubuntu/activemq@5.13.2+dfsg-2ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.6.0+dfsg1-4+deb8u1ubuntu1",
"5.6.0+dfsg1-5",
"5.13.2+dfsg-2",
"5.13.2+dfsg-2ubuntu0.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "activemq",
"binary_version": "5.15.8-2~18.04.1~esm1"
},
{
"binary_name": "libactivemq-java",
"binary_version": "5.15.8-2~18.04.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "activemq",
"purl": "pkg:deb/ubuntu/activemq@5.15.8-2~18.04.1~esm1?arch=source\u0026distro=esm-apps/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.14.5-3",
"5.15.2-2",
"5.15.3-2",
"5.15.8-2~18.04",
"5.15.8-2~18.04.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "activemq",
"binary_version": "5.15.11-1ubuntu0.1~esm1"
},
{
"binary_name": "libactivemq-java",
"binary_version": "5.15.11-1ubuntu0.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "activemq",
"purl": "pkg:deb/ubuntu/activemq@5.15.11-1ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.10-1",
"5.15.11-1",
"5.15.11-1ubuntu0.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "activemq",
"binary_version": "5.16.1-1ubuntu0.1"
},
{
"binary_name": "libactivemq-java",
"binary_version": "5.16.1-1ubuntu0.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:22.04:LTS",
"name": "activemq",
"purl": "pkg:deb/ubuntu/activemq@5.16.1-1ubuntu0.1?arch=source\u0026distro=esm-apps/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.16.1-1",
"5.16.1-1ubuntu0.1~esm1",
"5.16.1-1ubuntu0.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "activemq",
"binary_version": "5.17.6+dfsg-1"
},
{
"binary_name": "libactivemq-java",
"binary_version": "5.17.6+dfsg-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "activemq",
"purl": "pkg:deb/ubuntu/activemq@5.17.6+dfsg-1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.17.2+dfsg-2",
"5.17.6+dfsg-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "activemq",
"binary_version": "5.17.6+dfsg-2"
},
{
"binary_name": "libactivemq-java",
"binary_version": "5.17.6+dfsg-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "activemq",
"purl": "pkg:deb/ubuntu/activemq@5.17.6+dfsg-2?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.17.6+dfsg-1",
"5.17.6+dfsg-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "activemq",
"binary_version": "5.17.6+dfsg-2ubuntu1"
},
{
"binary_name": "libactivemq-java",
"binary_version": "5.17.6+dfsg-2ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "activemq",
"purl": "pkg:deb/ubuntu/activemq@5.17.6+dfsg-2ubuntu1?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.17.6+dfsg-2",
"5.17.6+dfsg-2ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "activemq",
"binary_version": "5.17.6+dfsg-2"
},
{
"binary_name": "libactivemq-java",
"binary_version": "5.17.6+dfsg-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "activemq",
"purl": "pkg:deb/ubuntu/activemq@5.17.6+dfsg-2?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.17.6+dfsg-2"
]
}
],
"aliases": [],
"details": "Missing Authentication for Critical Function (CWE-306) vulnerability in Apache Artemis, Apache ActiveMQ Artemis. An unauthenticated remote attacker can use the Core protocol to force a target broker to establish an outbound Core federation connection to an attacker-controlled rogue broker. This could potentially result in message injection into any queue and/or message exfiltration from any queue via the rogue broker. This impacts environments that allow both: - incoming Core protocol connections from untrusted sources to the broker - outgoing Core protocol connections from the broker to untrusted targets This issue affects: - Apache Artemis from 2.50.0 through 2.51.0 - Apache ActiveMQ Artemis from 2.11.0 through 2.44.0. Users are recommended to upgrade to Apache Artemis version 2.52.0, which fixes the issue. The issue can be mitigated by one of the following: - Remove Core protocol support from any acceptor receiving connections from untrusted sources. Incoming Core protocol connections are supported by default via the \"artemis\" acceptor listening on port 61616. See the \"protocols\" URL parameter configured for the acceptor. An acceptor URL without this parameter supports all protocols by default, including Core. - Use two-way SSL (i.e. certificate-based authentication) in order to force every client to present the proper SSL certificate when establishing a connection before any message protocol handshake is attempted. This will prevent unauthenticated exploitation of this vulnerability. - Implement and deploy a Core interceptor to deny all Core downstream federation connect packets. Such packets have a type of (int) -16 or (byte)\u00a00xfffffff0. Documentation for interceptors is available at https://artemis.apache.org/components/artemis/documentation/latest/intercepting-operations.html .",
"id": "UBUNTU-CVE-2026-27446",
"modified": "2026-10-28T17:33:51Z",
"published": "2026-03-04T09:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-27446"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27446"
},
{
"type": "REPORT",
"url": "https://lists.apache.org/thread/jwpsdc8tdxotm98od8n8n30fqlzoc8gg"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:L/SI:L/SA:L",
"type": "CVSS_V4"
},
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-27446"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.