Skip to main content
CVE-2026-44236VulnerabilityPublished Updated

Bundesamt für Sicherheit in der Informationstechnik Open Source · RabbitMQ: Schwachstelle ermöglicht Denial of Service

Affects Bundesamt für Sicherheit in der Informationstechnik Open SourceSource GCVE Database

0
Compare
Authoritative record:CVE-2026-44236· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 0.16.0 soon.

Data as of 12 Nov 2026, 12:20 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.16.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

Upgrade rabbitmq-c and alanxz/rabbitmq-c to 0.16.0.

Affected software

ProductAffectedFixed in
alanxzrabbitmq-cAffected
  • <0.16.0
Fixed in
  • 0.16.0
GitHubalanxz/rabbitmq-cpkg:github/alanxz/rabbitmq-cOther threatsAffected
  • <0.16.0
Fixed in
  • 0.16.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patch by upgrading librabbitmq to version 0.16.0 or later. Red Hat has released updated packages for affected distributions. Follow the vendor advisory instructions to update affected systems accordingly.

Description

A heap buffer overflow vulnerability in the librabbitmq client library for AMQP protocol version 0-9-1 can lead to denial of service. This affects RabbitMQ clients using versions prior to 0.16.0. The issue has been fixed in version 0.16.0.

References

Community reviews

Loading reviews…