CVE-2026-5450

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-20. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

Calling the scanf family of functions with a %mc (malloc'd character match) in the GNU C Library version 2.7 to version 2.43 with a format width specifier with an explicit width greater than 1024 could result in a one byte heap buffer overflow.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
39.6%
KEV
Not listed

Published

April 20, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

34008 – (CVE-2026-5450) stdio-common: scanf %mc pattern will cause heap overflow when width > 1024

https://sourceware.org/bugzilla/show_bug.cgi?id=CVE-2026-5450
generic

The GNU C Library security advisories update for 2026-04-20

https://inbox.sourceware.org/libc-announce/[email protected]/T/#u

Vendor Advisories for CVE-2026-5450(15)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatglibc-main-2.42-12.hum12026-05-01redhat

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.

Data Freshness Timeline

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

Showing the most recent 100 of 239 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-5450?
CVE-2026-5450 is a critical vulnerability published on April 20, 2026. Calling the scanf family of functions with a %mc (malloc'd character match) in the GNU C Library version 2.7 to version 2.43 with a format width specifier with an explicit width greater than 1024 could result in a one byte heap buffer overflow.
When was CVE-2026-5450 disclosed?
CVE-2026-5450 was first published in the National Vulnerability Database on April 20, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5450 actively exploited?
CVE-2026-5450 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-5450?
CVE-2026-5450 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-5450?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5450, 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-2026-5450

Explore →

Is Your Infrastructure Affected by CVE-2026-5450?

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

Start Free Scan →Browse All CVEs