Secuno
ENNL
Book demo

CVE-2026-40200

8.1 HIGHEPSS 0.17%
  1. Published10 Apr 2026

Description

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 3.1 breakdown

Attack vectorLocal
Attack complexityHigh
Privileges requiredNone
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-967609.8
Authlib (v1.7.2 and below) contains a signature verification bypass vulnerability. The…
CVE-2026-163929.1
JIT miscompilation in the JavaScript Engine: JIT component. This vulnerability was…
CVE-2026-76568.1
The IPv6 Neighbor Discovery handlers in subsys/net/ip/ipv6_nbr.c (handle_ra_input,…
CVE-2026-552769.1
Always-Incorrect Control Flow Implementation vulnerability in Apache Tomcat meant that…
CVE-2026-409608.1
Luanti 5 before 5.15.2 sometimes allows unintended access to an insecure environment.…
CVE-2025-433599.8
A logic issue was addressed with improved state management. This issue is fixed in iOS…

Frequently asked

Is CVE-2026-40200 being actively exploited?

CVE-2026-40200 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.17%.

How severe is CVE-2026-40200?

CVE-2026-40200 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.17% probability of exploitation.

How do I fix CVE-2026-40200?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-40200 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.