CVE-2026-44236

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th 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
Trending — 3 sources updated this weekElevated

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

7.1EG
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.4%CVSS: 7.1Exploit: 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 connection.tune.frame_max value during amqp_login(), and rabbitmq-c accepts the value in amqp_login_inner() in librabbitmq/amqp_socket.c. amqp_tune_connection() in librabbitmq/amqp_connection.c uses frame_max to reallocate the outbound buffer without enforcing AMQP_FRAME_MIN_SIZE. Immediate serialization of connection.tune-ok through amqp_frame_to_bytes() writes beyond the undersized heap allocation, causing memory corruption and likely denial of service. An on-path attacker can also trigger the flaw against plaintext AMQP traffic. Code execution is theoretically possible but was not demonstrated. This issue is fixed in version 0.16.0.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 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.4%
EPSS %ILE
34th
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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 24, 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 4777d0b5c58c (alanxz/rabbitmq-c)

Patch available: alanxz/rabbitmq-c v0.16.0 (contains commit 4777d0b5c58c)

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

Release v0.16.0

Patch available: alanxz/rabbitmq-c v0.17.0 (PR #879 merged 2026-06-09)

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

Heap buffer overflow in AMQP login handshake via undersized connection.tune.frame_max · Advisory · alanxz/rabbitmq-c · GitHub

https://github.com/alanxz/rabbitmq-c/security/advisories/GHSA-jh48-qjf5-fx5v

Vendor Advisories for CVE-2026-44236(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibrabbitmq1 (0.4.1-1ubuntu0.1~esm2) @ trusty2026-11-01ubuntu
ubuntulibrabbitmq4 (0.15.0-1ubuntu0.26.04.1) @ resolute2026-11-01ubuntu
redhatlibrabbitmq-0:0.14.0-3.el10_2.12026-10-19redhat
redhatlibrabbitmq-0:0.11.0-7.el9_8.12026-10-13redhat
redhatlibrabbitmq-0:0.9.0-6.el8_102026-10-05redhat

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(1)

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

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 67× 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.

Showing the most recent 100 of 124 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 24 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

2 shown

ubuntu:USN-8437-1

Frequently asked(5)

What is CVE-2026-44236?
CVE-2026-44236 is a high-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 connection.tune.frame_max value during amqp_login(), and rabbitmq-c accepts the value in amqp_login_inner() in librabbitmq/amqp_socket.c. amqp_tune_connection() in…
When was the CVE record for CVE-2026-44236 published?
The CVE record for CVE-2026-44236 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 24, 2026; the record at its source may have been updated since.
Is CVE-2026-44236 actively exploited?
CVE-2026-44236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44236?
CVE-2026-44236 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44236?
A fix for CVE-2026-44236 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44236 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-44236?

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

Book a Demo →Browse All CVEs