ubuntu-cve-2026-44393
Vulnerability from osv_ubuntu
An issue was discovered in OpenStack oslo.messaging 1.0.0 through 17.3.0. The oslo.messaging RabbitMQ driver does not perform TLS hostname verification when connecting to the message broker. When ssl_ca_file is configured, the driver enables certificate chain validation but does not pass the expected broker hostname into the underlying TLS stack. Any certificate signed by the deployment CA is accepted regardless of hostname, allowing an attacker who can intercept control-plane traffic to impersonate the RabbitMQ broker and perform a man-in-the-middle attack on RPC and notification traffic. All OpenStack services using oslo.messaging with RabbitMQ over TLS are affected.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "oslo-messaging-zmq-receiver",
"binary_version": "4.6.1-2ubuntu2"
},
{
"binary_name": "python-oslo-messaging",
"binary_version": "4.6.1-2ubuntu2"
},
{
"binary_name": "python-oslo.messaging",
"binary_version": "4.6.1-2ubuntu2"
},
{
"binary_name": "python3-oslo.messaging",
"binary_version": "4.6.1-2ubuntu2"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "python-oslo.messaging",
"purl": "pkg:deb/ubuntu/python-oslo.messaging@4.6.1-2ubuntu2?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.5.0-1ubuntu1",
"3.0.0-1ubuntu2",
"4.5.0-1ubuntu1",
"4.5.1-1ubuntu1",
"4.6.1-2ubuntu1",
"4.6.1-2ubuntu2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "oslo-messaging-zmq-receiver",
"binary_version": "5.35.0-0ubuntu4"
},
{
"binary_name": "python-oslo.messaging",
"binary_version": "5.35.0-0ubuntu4"
},
{
"binary_name": "python3-oslo.messaging",
"binary_version": "5.35.0-0ubuntu4"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "python-oslo.messaging",
"purl": "pkg:deb/ubuntu/python-oslo.messaging@5.35.0-0ubuntu4?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.30.0-0ubuntu1",
"5.33.1-0ubuntu1",
"5.34.1-0ubuntu1",
"5.35.0-0ubuntu1",
"5.35.0-0ubuntu2",
"5.35.0-0ubuntu3",
"5.35.0-0ubuntu4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-oslo.messaging",
"binary_version": "12.1.6-0ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "python-oslo.messaging",
"purl": "pkg:deb/ubuntu/python-oslo.messaging@12.1.6-0ubuntu1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"9.7.1-0ubuntu3",
"10.4.0-0ubuntu2",
"10.5.0-0ubuntu1",
"11.0.0-0ubuntu1",
"12.1.0-0ubuntu1",
"12.1.6-0ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-oslo.messaging",
"binary_version": "12.13.0-0ubuntu1.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "python-oslo.messaging",
"purl": "pkg:deb/ubuntu/python-oslo.messaging@12.13.0-0ubuntu1.2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"12.9.1-0ubuntu4",
"12.11.0-0ubuntu1",
"12.11.1-0ubuntu1",
"12.13.0-0ubuntu1",
"12.13.0-0ubuntu1.1",
"12.13.0-0ubuntu1.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-oslo.messaging",
"binary_version": "14.6.0-0ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "python-oslo.messaging",
"purl": "pkg:deb/ubuntu/python-oslo.messaging@14.6.0-0ubuntu1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"14.4.1-0ubuntu1",
"14.6.0-0ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-oslo.messaging",
"binary_version": "17.1.0-0ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "python-oslo.messaging",
"purl": "pkg:deb/ubuntu/python-oslo.messaging@17.1.0-0ubuntu1?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"16.1.0-0ubuntu1",
"17.1.0-0ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-oslo.messaging",
"binary_version": "17.3.0-2ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "python-oslo.messaging",
"purl": "pkg:deb/ubuntu/python-oslo.messaging@17.3.0-2ubuntu1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"17.1.0-0ubuntu1",
"17.2.0-0ubuntu1",
"17.3.0-2ubuntu1"
]
}
],
"aliases": [],
"details": "An issue was discovered in OpenStack oslo.messaging 1.0.0 through 17.3.0. The oslo.messaging RabbitMQ driver does not perform TLS hostname verification when connecting to the message broker. When ssl_ca_file is configured, the driver enables certificate chain validation but does not pass the expected broker hostname into the underlying TLS stack. Any certificate signed by the deployment CA is accepted regardless of hostname, allowing an attacker who can intercept control-plane traffic to impersonate the RabbitMQ broker and perform a man-in-the-middle attack on RPC and notification traffic. All OpenStack services using oslo.messaging with RabbitMQ over TLS are affected.",
"id": "UBUNTU-CVE-2026-44393",
"modified": "2026-06-30T16:21:56Z",
"published": "2026-06-04T16:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-44393"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44393"
},
{
"type": "REPORT",
"url": "https://wiki.openstack.org/wiki/OSSN/OSSN-0096"
},
{
"type": "REPORT",
"url": "https://launchpad.net/bugs/2150316"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-44393"
]
}
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.
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.