CVE-2026-2681 A flaw was found in the blst cryptographic library.

Medium 5.3 Published Updated

A remote attacker can cause a denial of service in applications using the blst library by triggering an out-of-bounds stack write during key generation.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-2681?

CVE-2026-2681 is a medium-severity memory corruption vulnerability, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

A flaw was found in the blst cryptographic library. This out-of-bounds stack write vulnerability, specifically in the blst_sha256_bcopy assembly routine, occurs due to a missing zero-length guard. A remote attacker can exploit this by providing a zero-length salt parameter to key generation functions, such as blst_keygen_v5(), if the application exposes this functionality. Successful exploitation leads to memory corruption and immediate process termination, resulting in a denial-of-service (DoS) condition.

Weakness: CWE-787

Which versions are affected by CVE-2026-2681?

How do I fix CVE-2026-2681?

No fix has been published for CVE-2026-2681 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-2681 being exploited?

There is no known exploitation of CVE-2026-2681 in the wild and no public exploit code.

Sources

Also known as GHSA-6ff8-r7x3-m73p.

Is CVE-2026-2681 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free