CVE-2026-44235

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-82333 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 17, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 17, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

rabbitmq-c v0.16.0

Patch available: alanxz/rabbitmq-c v0.16.0

https://github.com/alanxz/rabbitmq-c/releases/tag/v0.16.0
GitHub commit Patch Available

commit 1d3afbb056fe (alanxz/rabbitmq-c)

Patch available: alanxz/rabbitmq-c v0.16.0 (contains commit 1d3afbb056fe)

https://github.com/alanxz/rabbitmq-c/commit/1d3afbb056fee5cc9ea05680bf32288715d0d802
GitHub pull request Patch Available

amqp_connection: reject undersized frames in amqp_handle_input (GHSA-9mmv-r8g3-qp46)

Patch available: alanxz/rabbitmq-c v0.16.0 (PR #878 merged 2026-06-08)

https://github.com/alanxz/rabbitmq-c/pull/878
GitHub advisoryMentions a patch (unverified)

size_t underflow in AMQP frame length computation leads to out-of-bounds read in rabbitmq-c · Advisory · alanxz/rabbitmq-c · GitHub

https://github.com/alanxz/rabbitmq-c/security/advisories/GHSA-9mmv-r8g3-qp46

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibrabbitmq4 (0.15.0-1ubuntu0.26.04.1) @ resolute2026-10-23ubuntu
ubuntulibrabbitmq1 (0.4.1-1ubuntu0.1~esm2) @ trusty2026-10-23ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
librabbitmq0.11.0-1, 0.11.0-1+deb12u1
  • every version up to 0.11.0-1+deb12u2: fixed in 0.11.0-1+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
librabbitmq0.15.0-1
  • every version up to 0.15.0-1+deb13u1: fixed in 0.15.0-1+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
librabbitmq0.15.0-1
  • every version up to 0.16.0-1: fixed in 0.16.0-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 53× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-10-30 16:25 UTCOSV refresh
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-25 14:27 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-23 01:35 UTCEG score recompute
  14. 2026-10-23 01:35 UTCVendor advisory
  15. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-18 03:39 UTCEG score recompute
  21. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
Show 65 more
  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-12 16:05 UTCEG score recompute
  3. 2026-10-11 19:47 UTCEG score recompute
  4. 2026-10-11 17:02 UTCEG score recompute
  5. 2026-10-11 14:27 UTCEG score recompute
  6. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-10-10 22:38 UTCEG score recompute
  8. 2026-10-10 22:38 UTCVendor advisory
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-09 22:13 UTCEG score recompute
  11. 2026-10-09 22:13 UTCVendor advisory
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-10-08 21:48 UTCEG score recompute
  14. 2026-10-08 21:48 UTCVendor advisory
  15. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-10-07 20:54 UTCVendor advisory
  18. 2026-10-06 20:19 UTCEG score recompute
  19. 2026-10-06 20:19 UTCVendor advisory
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-10-05 19:51 UTCEG score recompute
  22. 2026-10-05 19:51 UTCVendor advisory
  23. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  24. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-04 19:30 UTCVendor advisory
  26. 2026-10-03 19:08 UTCEG score recompute
  27. 2026-10-03 19:08 UTCVendor advisory
  28. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  29. 2026-10-02 18:48 UTCEG score recompute
  30. 2026-10-02 18:48 UTCVendor advisory
  31. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  32. 2026-10-01 18:26 UTCVendor advisory
  33. 2026-09-30 17:49 UTCEG score recompute
  34. 2026-09-30 17:49 UTCVendor advisory
  35. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  36. 2026-09-30 00:43 UTCEG score recompute
  37. 2026-09-30 00:43 UTCVendor advisory
  38. 2026-09-28 23:34 UTCEG score recompute
  39. 2026-09-28 23:34 UTCVendor advisory
  40. 2026-09-27 23:13 UTCEG score recompute
  41. 2026-09-27 23:13 UTCVendor advisory
  42. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  43. 2026-09-26 22:51 UTCEG score recompute
  44. 2026-09-26 22:51 UTCVendor advisory
  45. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  46. 2026-09-25 22:30 UTCVendor advisory
  47. 2026-09-24 21:30 UTCEG score recompute
  48. 2026-09-24 21:30 UTCVendor advisory
  49. 2026-09-23 20:38 UTCEG score recompute
  50. 2026-09-23 20:38 UTCVendor advisory
  51. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  52. 2026-09-22 20:16 UTCEG score recompute
  53. 2026-09-22 20:16 UTCVendor advisory
  54. 2026-09-21 19:52 UTCEG score recompute
  55. 2026-09-21 19:52 UTCVendor advisory
  56. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  57. 2026-09-20 19:31 UTCVendor advisory
  58. 2026-09-19 19:10 UTCEG score recompute
  59. 2026-09-19 19:10 UTCVendor advisory
  60. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  61. 2026-09-18 18:47 UTCVendor advisory
  62. 2026-09-17 18:26 UTCEG score recompute
  63. 2026-09-17 18:26 UTCVendor advisory
  64. 2026-09-17 17:20 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
  65. 2026-09-17 17:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-44235?
CVE-2026-44235 is a medium-severity vulnerability; its CVE record was published on September 17, 2026. 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,…
When was the CVE record for CVE-2026-44235 published?
The CVE record for CVE-2026-44235 was published on September 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-44235 actively exploited?
CVE-2026-44235 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44235?
CVE-2026-44235 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44235?
A fix for CVE-2026-44235 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44235

Explore →

Is Your Infrastructure Affected by CVE-2026-44235?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.