CVE-2026-44393

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-06-04. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

Published

June 4, 2026

Last Modified

August 27, 2026

Advisory Details (2)

Auto-updated Jun 9, 2026
Patch available.
generic

OSSN/OSSN-0096 - OpenStack

https://wiki.openstack.org/wiki/OSSN/OSSN-0096
generic

Bug #2150316 “[OSSN-0096] oslo.messaging does not verify RabbitM...” : Bugs : oslo.messaging

https://bugs.launchpad.net/oslo.messaging/+bug/2150316

Vendor Advisories for CVE-2026-44393(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython-oslo-messaging-0:10.2.4-2.20260710155333.82281a0.el8ost2026-08-13redhat
piposlo.messaging—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-oslo.messaging12.12.0-1 ... 17.3.0-4 (37 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-oslo.messaging14.0.0-2
  • every version up to 14.0.3-0+deb12u1: fixed in 14.0.3-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-oslo.messaging16.1.0-3
  • every version up to 16.1.0-3+deb13u1: fixed in 16.1.0-3+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-oslo.messaging16.1.0-3 ... 17.3.0-3 (7 versions)
  • every version up to 17.3.0-4: fixed in 17.3.0-4
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
oslo-messaging1.10.0 ... 9.8.0 (237 versions)
  • 1.0.0 through 17.3.0: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 255 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-27 13:48 UTCEPSS rescore
  11. 2026-09-26 15:58 UTCEPSS rescore
  12. 2026-09-23 17:53 UTCEPSS rescore
  13. 2026-09-20 20:15 UTCEPSS rescore
  14. 2026-09-18 19:28 UTCEPSS rescore
  15. 2026-09-17 19:31 UTCEPSS rescore
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-14 05:28 UTCEG score recompute
  19. 2026-09-14 05:28 UTCVendor advisory
  20. 2026-09-14 05:28 UTCGHSA enrichment
  21. 2026-09-13 16:47 UTCEPSS rescore
  22. 2026-09-12 15:01 UTCEPSS rescore
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 09:37 UTCEPSS rescore
  25. 2026-09-10 09:34 UTCEPSS rescore
Show 75 more
  1. 2026-09-08 22:00 UTCEPSS rescore
  2. 2026-09-07 16:01 UTCEPSS rescore
  3. 2026-09-06 13:47 UTCEPSS rescore
  4. 2026-09-04 05:06 UTCEPSS rescore
  5. 2026-09-02 14:12 UTCEPSS rescore
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-27 13:34 UTCVendor advisory
  11. 2026-08-27 13:34 UTCGHSA enrichment
  12. 2026-08-27 13:01 UTCEG score recompute
  13. 2026-08-27 13:01 UTCVendor advisory
  14. 2026-08-27 13:01 UTCGHSA enrichment
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-25 03:35 UTCEG score recompute
  18. 2026-08-25 03:35 UTCVendor advisory
  19. 2026-08-25 03:35 UTCGHSA enrichment
  20. 2026-08-24 01:16 UTCVendor advisory
  21. 2026-08-24 01:16 UTCGHSA enrichment
  22. 2026-08-23 12:45 UTCEG score recompute
  23. 2026-08-23 12:45 UTCVendor advisory
  24. 2026-08-23 12:45 UTCGHSA enrichment
  25. 2026-08-23 00:19 UTCEPSS rescore
  26. 2026-08-21 23:49 UTCEPSS rescore
  27. 2026-08-21 14:38 UTCEG score recompute
  28. 2026-08-21 14:38 UTCVendor advisory
  29. 2026-08-21 14:38 UTCGHSA enrichment
  30. 2026-08-20 22:55 UTCEPSS rescore
  31. 2026-08-20 22:30 UTCVendor advisory
  32. 2026-08-20 22:30 UTCGHSA enrichment
  33. 2026-08-20 09:59 UTCEG score recompute
  34. 2026-08-20 09:59 UTCVendor advisory
  35. 2026-08-20 09:59 UTCGHSA enrichment
  36. 2026-08-19 17:04 UTCEPSS rescore
  37. 2026-08-18 13:48 UTCEPSS rescore
  38. 2026-08-17 13:47 UTCEPSS rescore
  39. 2026-08-17 04:09 UTCVendor advisory
  40. 2026-08-17 04:09 UTCGHSA enrichment
  41. 2026-08-16 15:38 UTCEG score recompute
  42. 2026-08-16 15:38 UTCVendor advisory
  43. 2026-08-16 15:38 UTCGHSA enrichment
  44. 2026-08-16 14:56 UTCEPSS rescore
  45. 2026-08-16 03:07 UTCEG score recompute
  46. 2026-08-16 03:07 UTCVendor advisory
  47. 2026-08-16 03:07 UTCGHSA enrichment
  48. 2026-08-16 02:14 UTCEPSS rescore
  49. 2026-08-15 14:37 UTCVendor advisory
  50. 2026-08-15 14:37 UTCGHSA enrichment
  51. 2026-08-15 01:57 UTCEG score recompute
  52. 2026-08-15 01:57 UTCVendor advisory
  53. 2026-08-15 01:57 UTCGHSA enrichment
  54. 2026-08-15 01:30 UTCEPSS rescore
  55. 2026-08-14 13:27 UTCVendor advisory
  56. 2026-08-14 13:27 UTCGHSA enrichment
  57. 2026-08-14 12:29 UTCVendor advisory
  58. 2026-08-14 12:29 UTCGHSA enrichment
  59. 2026-08-14 11:20 UTCGHSA enrichment
  60. 2026-08-13 22:49 UTCEG score recompute
  61. 2026-08-13 22:49 UTCGHSA enrichment
  62. 2026-08-13 22:00 UTCEPSS rescore
  63. 2026-08-13 04:14 UTCGHSA enrichment
  64. 2026-08-12 15:44 UTCEG score recompute
  65. 2026-08-12 15:44 UTCGHSA enrichment
  66. 2026-08-12 13:51 UTCEPSS rescore
  67. 2026-08-12 02:42 UTCGHSA enrichment
  68. 2026-08-11 14:11 UTCGHSA enrichment
  69. 2026-08-11 01:38 UTCEG score recompute
  70. 2026-08-11 01:38 UTCGHSA enrichment
  71. 2026-08-11 00:00 UTCEPSS rescore
  72. 2026-08-10 13:08 UTCGHSA enrichment
  73. 2026-08-10 00:37 UTCEG score recompute
  74. 2026-08-10 00:37 UTCGHSA enrichment
  75. 2026-08-09 13:46 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44393?
CVE-2026-44393 is a high vulnerability published on June 4, 2026. 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 sslcafile is configured, the driver enables certificate chain validation but does not pass the expected…
When was CVE-2026-44393 disclosed?
CVE-2026-44393 was first published on June 4, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44393 actively exploited?
CVE-2026-44393 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44393?
CVE-2026-44393 has a CVSS v3.1 base score of 7.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-44393?
A fix for CVE-2026-44393 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44393 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44393

Explore →

Is Your Infrastructure Affected by CVE-2026-44393?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs