# CVE-2026-44235: rabbitmq-c: size_t underflow in AMQP frame length computation leads to out-of-bounds read

> A malicious AMQP server can trigger an integer underflow in rabbitmq-c, causing an out-of-bounds read and application crash.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** AZL-105084, BIT-rabbitmq-c-2026-44235, DEBIAN-CVE-2026-44235, ECHO-0351-ee63-bf06, GHSA-9mmv-r8g3-qp46, UBUNTU-CVE-2026-44235

## What is CVE-2026-44235?

CVE-2026-44235 is a medium-severity vulnerability in alanxz rabbitmq-c, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

rabbitmq-c is a C-language AMQP client library for RabbitMQ. Prior to 0.16.0, a malicious AMQP server can send an undersized HEADER or METHOD frame during client login and cause unsigned size_t underflow in amqp_handle_input() in librabbitmq/amqp_connection.c. The parser subtracts HEADER_SIZE, fixed per-frame fields, and FOOTER_SIZE from state->target_size without first checking the minimum frame length. The wrapped encoded.len value is passed through amqp_decode_properties() to amqp_decode_table_internal(), where it defeats bounds checks and causes an out-of-bounds read and process crash. An on-path attacker can also trigger the issue when AMQP traffic is not protected by TLS with certificate validation. The demonstrated impact is denial of service, with no reliable memory disclosure or code execution shown. This issue is fixed in version 0.16.0.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound)), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-44235?

1 open source package ship an affected version, including rabbitmq-c.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rabbitmq-c` | Bitnami | All versions | 0.16.0 |

## How do I fix CVE-2026-44235?

Upgrade rabbitmq-c to 0.16.0 or later.

## Is CVE-2026-44235 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44235 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44235 and fix it if it is affected.

What it is: CVE-2026-44235 is a medium-severity vulnerability in alanxz rabbitmq-c, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44235 exists.

Affected packages and fixed versions:
- rabbitmq-c (Bitnami): affected all versions; fixed in 0.16.0

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44235/ (Markdown: https://insights.sbomify.com/CVE-2026-44235/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44235
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44235
- OSV: https://osv.dev/vulnerability/CVE-2026-44235

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44235/
Summaries are generated and may contain mistakes; the official description above is the record.
