CVE-2024-21646

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 5.1% (92nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2024-19279 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5.1%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Azure uAMQP is a general purpose C library for AMQP 1.0. The UAMQP library is used by several clients to implement AMQP protocol communication. When clients using this library receive a crafted binary type data, an integer overflow or wraparound or memory safety issue can occur and may cause remote code execution. This vulnerability has been patched in release 2024-01-01.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation5.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
5.1%
EPSS %ILE
92nd
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
5.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

January 9, 2024

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Nov 1, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Azure IoT Platform Device SDK Remote Code Execution Vulnerability · Advisory · Azure/azure-uamqp-c · GitHub

https://github.com/Azure/azure-uamqp-c/security/advisories/GHSA-j29m-p99g-7hpv
GitHub commit

commit 12ddb3a31a5a (Azure/azure-uamqp-c)

Fix landed in Azure/azure-uamqp-c commit 12ddb3a31a5a — awaiting tagged release

https://github.com/Azure/azure-uamqp-c/commit/12ddb3a31a5a97f55b06fa5d74c59a1d84ad78fe

Vendor Advisories for CVE-2024-21646(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
azure-uamqp-python1.2.13-1 ... 1.6.9-3 (21 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
azure-uamqp-python1.5.3-1 ... 1.6.9-3 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
azure-uamqp-python—
  • every version up to 1.6.8-1: fixed in 1.6.8-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
azure-uamqp-python—
  • every version up to 1.6.8-1: fixed in 1.6.8-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 66× 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 99 of 232 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 133 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-21646?
CVE-2024-21646 is a critical-severity vulnerability; its CVE record was published on January 9, 2024. Azure uAMQP is a general purpose C library for AMQP 1.0. The UAMQP library is used by several clients to implement AMQP protocol communication. When clients using this library receive a crafted binary type data, an integer overflow or wraparound or memory safety issue can occur and may cause remote…
When was the CVE record for CVE-2024-21646 published?
The CVE record for CVE-2024-21646 was published on January 9, 2024. 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2024-21646 actively exploited?
CVE-2024-21646 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.1% probability of exploitation in the next 30 days (92nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-21646?
CVE-2024-21646 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-21646?
A fix for CVE-2024-21646 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-21646 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-2024-21646

Explore →

Is Your Infrastructure Affected by CVE-2024-21646?

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