CVE-2026-40200

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-04-10. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based memory corruption can occur during qsort of very large arrays, due to incorrectly implemented double-word primitives. The number of elements must exceed about seven million, i.e., the 32nd Leonardo number on 32-bit platforms (or the 64th Leonardo number on 64-bit platforms, which is not practical).

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

April 10, 2026

Last Modified

April 27, 2026

Advisory Details (3)

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

oss-security - CVE-2026-40200: musl libc: stack corruption in qsort with sufficiently large inputs

http://www.openwall.com/lists/oss-security/2026/04/10/13
generic

oss-security - CVE-2026-40200: musl libc: stack corruption in qsort with sufficiently large inputs

https://www.openwall.com/lists/oss-security/2026/04/10/13
generic

musl libc Release History

https://musl.libc.org/releases.html

Affected Packages

(10 across 10 ecosystems)
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
musl—1.2.4_git20230717-r6—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
musl—1.2.5-r3—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
musl—1.2.5-r11—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
musl—1.2.5-r12—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
musl—1.2.5-r23—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
musl—1.2.6-r2—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
musl1.2.2-1 ... 1.2.6-1 (14 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
musl1.2.3-1 ... 1.2.6-1 (10 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
musl1.2.5-31.2.5-3.1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
musl1.2.5-3, 1.2.5-3.1~deb13u11.2.5-3.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 24× 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 174 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-40200?
CVE-2026-40200 is a high vulnerability published on April 10, 2026. An issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based memory corruption can occur during qsort of very large arrays, due to incorrectly implemented double-word primitives. The number of elements must exceed about seven million, i.e., the 32nd Leonardo number on 32-bit platforms (or…
When was CVE-2026-40200 disclosed?
CVE-2026-40200 was first published in the National Vulnerability Database on April 10, 2026, with the most recent update on April 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40200 actively exploited?
CVE-2026-40200 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-40200?
CVE-2026-40200 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-40200?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40200, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-40200?

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

Start Free Scan →Browse All CVEs