{"answers":{"affected":"3 open source packages ship an affected version, including oslo-messaging and oslo.messaging.","exploited":"There is no known exploitation of CVE-2026-44393 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-44393 is a high-severity vulnerability in n/a, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44393 and fix it if it is affected.\n\nWhat it is: CVE-2026-44393 is a high-severity vulnerability in n/a, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-44393 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- oslo-messaging (PyPI): affected from 1.0.0 up to 17.3.0; no fix listed\n- oslo-messaging (PyPI): affected from 1.0.0 up to 17.3.0; no fix listed\n- oslo.messaging (PyPI): affected from 1.0.0 up to 17.3.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44393/ (Markdown: https://insights.sbomify.com/CVE-2026-44393/index.md)","id":"CVE-2026-44393","markdown":"https://insights.sbomify.com/CVE-2026-44393/index.md","name":"CVE-2026-44393","record":{"aliases":["DEBIAN-CVE-2026-44393","GHSA-76qh-xr7q-h39m","PYSEC-2026-3492","UBUNTU-CVE-2026-44393","openSUSE-SU-2026:10973-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenStack messaging library","requires_auth":"none","summary":"Attackers can intercept OpenStack RPC traffic via man-in-the-middle attacks due to missing TLS hostname verification in the RabbitMQ driver.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"},{"id":"CWE-297","name":"Improper Validation of Certificate with Host Mismatch"}],"description":"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.","ecosystems":["PyPI","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"OpenStack oslo.messaging does not verify RabbitMQ broker hostname during TLS handshake","id":"CVE-2026-44393","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":4,"n_references":2,"next":{"headline":"OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token","id":"CVE-2026-44394"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["1.0.0"],"last_affected":["17.3.0"],"package":"oslo-messaging","purl":"pkg:pypi/oslo-messaging","source":"GHSA-76qh-xr7q-h39m"},{"ecosystem":"PyPI","fixed":[],"introduced":["1.0.0"],"last_affected":["17.3.0"],"package":"oslo-messaging","purl":"pkg:pypi/oslo-messaging","source":"PYSEC-2026-3492"},{"ecosystem":"PyPI","fixed":[],"introduced":["1.0.0"],"last_affected":["17.3.0"],"package":"oslo.messaging","purl":null,"source":"GHSA-76qh-xr7q-h39m"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["18.1.0-1.1"],"introduced":["0"],"last_affected":[],"package":"python-oslo.messaging","purl":"pkg:rpm/opensuse/python-oslo.messaging\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:10973-1"}],"prev":{"headline":"Missing authorization in Movable Type","id":"CVE-2026-44392"},"products":["n/a"],"published":"2026-06-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-27","vendors":["n/a"]},"summary":"Attackers can intercept OpenStack RPC traffic via man-in-the-middle attacks due to missing TLS hostname verification in the RabbitMQ driver.","url":"https://insights.sbomify.com/CVE-2026-44393/"}