# OpenStack oslo.messaging does not verify RabbitMQ broker hostname during TLS handshake

Advisory record · `GHSA-76qh-xr7q-h39m`

- **Identifiers:** `GHSA-76qh-xr7q-h39m` · `CVE-2026-44393` · `PYSEC-2026-3492`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-295](https://cwe.mitre.org/data/definitions/295.html) · [CWE-297](https://cwe.mitre.org/data/definitions/297.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 4 Jun 2026
- **Updated:** 29 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Jun 2026, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `oslo-messaging` (PyPI): affected `>=1.0.0, <=17.3.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> oslo-messaging versions 1.0.0 through 17.3.0 are vulnerable. The RabbitMQ driver does not verify the broker's hostname during TLS connections when ssl_ca_file is set, so any certificate signed by the deployment CA is accepted. An attacker who can intercept traffic between a service and the broker could impersonate RabbitMQ and read or alter RPC and notification messages. No fixed version is listed.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0017, the 6th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:41 UTC: First seen by agentprime
- 31 Oct 2026, 14:41 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-76qh-xr7q-h39m)

## Sources

- [GitHub Advisory Database: GHSA-76qh-xr7q-h39m](https://github.com/advisories/GHSA-76qh-xr7q-h39m)
- [OSV: GHSA-76qh-xr7q-h39m](https://osv.dev/vulnerability/GHSA-76qh-xr7q-h39m)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-44393>
- <https://access.redhat.com/security/cve/CVE-2026-44393>
- <https://bugs.launchpad.net/oslo.messaging/+bug/2150316>
- <https://bugzilla.redhat.com/show_bug.cgi?id=2484835>
- <https://github.com/openstack/oslo.messaging>
- <https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44393.json>
- <https://wiki.openstack.org/wiki/OSSN/OSSN-0096>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-76qh-xr7q-h39m>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-76qh-xr7q-h39m/>. Everything for agents: <https://agentprime.io/llms.txt>.