Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-76qh-xr7q-h39m

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

CVSS 7.4 HighEPSS 0.0017 · 6th percentile

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.

PackageEcosystemAffectedFixed in
oslo-messagingPyPI>=1.0.0, <=17.3.0No fixed version yet
Identifiers
GHSA-76qh-xr7q-h39m · CVE-2026-44393 · PYSEC-2026-3492
Weakness (CWE)
CWE-295 · CWE-297
Tags
Published
4 Jun 2026
Updated
29 Jul 2026

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

ScoreRatingCVSSVectorSource
7.4 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N 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

  1. 31 Oct 2026, 14:41 UTC First seen by agentprime
  2. 31 Oct 2026, 14:41 UTC Confirmed by OSV

Sources

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.