CVE-2019-18609

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 3.3%, top 13% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

An issue was discovered in amqp_handle_input in amqp_connection.c in rabbitmq-c 0.9.0. There is an integer overflow that leads to heap memory corruption in the handling of CONNECTION_STATE_HEADER. A rogue server could return a malicious frame header that leads to a smaller target_size value than needed. This condition is then carried on to a memcpy function that copies too much data into a heap buffer.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation3% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
87.3%
KEV
Not listed

Published

December 1, 2019

Last Modified

November 21, 2024

Advisory Details (6)

Auto-updated Jun 13, 2026
Patch available. Sources: github_commit.
generic

rabbitmq-c/ChangeLog.md at master · alanxz/rabbitmq-c · GitHub

https://github.com/alanxz/rabbitmq-c/blob/master/ChangeLog.md
generic

RabbitMQ C client: Arbitrary code execution (GLSA 202003-07) — Gentoo security

https://security.gentoo.org/glsa/202003-07
generic

[SECURITY] Fedora 31 Update: librabbitmq-0.10.0-1.fc31 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XQER6XTKYMHNQR7QTHW7DJAH645WQROU/
generic

[SECURITY] Fedora 30 Update: librabbitmq-0.10.0-1.fc30 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WA7CPNVYMF6OQNIYNLWUY6U2GTKFOKH3/
generic

[SECURITY] [DLA 2022-1] librabbitmq security update

https://lists.debian.org/debian-lts-announce/2019/12/msg00004.html
github_commit Patch Available

commit fc85be712305 (alanxz/rabbitmq-c)

Patch available: alanxz/rabbitmq-c v0.10.0 (contains commit fc85be712305)

https://github.com/alanxz/rabbitmq-c/commit/fc85be7123050b91b054e45b91c78d3241a5047a

Vendor Advisories for CVE-2019-18609(2)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibrabbitmq4 (0.7.1-1ubuntu0.2) @ xenial2026-05-27ubuntu
ubuntulibrabbitmq-dev (0.9.0-0.2ubuntu0.19.10.1) @ eoan2026-05-27ubuntu
redhatlibrabbitmq-0:0.9.0-2.el82020-11-04redhat
redhatlibrabbitmq-0:0.8.0-3.el72020-09-29redhat

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.

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

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 15× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-18609?
CVE-2019-18609 is a critical vulnerability published on December 1, 2019. An issue was discovered in amqphandleinput in amqpconnection.c in rabbitmq-c 0.9.0. There is an integer overflow that leads to heap memory corruption in the handling of CONNECTIONSTATEHEADER. A rogue server could return a malicious frame header that leads to a smaller targetsize value than needed.…
When was CVE-2019-18609 disclosed?
CVE-2019-18609 was first published in the National Vulnerability Database on December 1, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-18609 actively exploited?
CVE-2019-18609 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 87.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-18609?
CVE-2019-18609 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-18609?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-18609, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-18609

Explore →

Is Your Infrastructure Affected by CVE-2019-18609?

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

Start Free Scan →Browse All CVEs