Skip to main content
VulnerabilityPublished Updated

CVE-2026-87737: Mirage crypto ec · Timing leak in NIST elliptic curves scalar multiplication

Affects mirage-crypto-ecSource GCVE Database

0

Mentioned vulnerabilities

CVSS 5.9 Medium : upgrade to 2.4.0 or 1a61aeee7f593ec067612df1739ec905eab0450f when convenient.

Data as of 10 Sep 2026, 14:35 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.4.0, 1a61aeee7f593ec067612df1739ec905eab0450f
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

What to do

Upgrade mirage-crypto-ec to 2.4.0 or 1a61aeee7f593ec067612df1739ec905eab0450f.

Affected software

ProductAffectedFixed in
opammirage-crypto-ecpkg:opam/mirage-crypto-ecOther threatsAffected
  • 2.0.0 – 2.3.0
  • >=0.11.3 <2.4.0
  • <1a61aeee7f593ec067612df1739ec905eab0450f
7 affected builds
Fixed in
  • 2.4.0
  • 1a61aeee7f593ec067612df1739ec905eab0450f

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in mirage-crypto-ec version 2.4.0, which replaces the secret-dependent table lookup with a constant-time approach. Users should upgrade to version 2.4.0 or later to remediate this vulnerability.

Description

A timing leak vulnerability exists in the scalar multiplication implementation of the mirage-crypto-ec library for NIST elliptic curves. The issue arises from secret-dependent table lookups that do not scan the entire pre-computed table, potentially leaking information through timing side channels. This flaw was introduced in version 0.11.3 and affects multiple versions up to but not including 2.4.0. The vulnerability was reported on August 12, 2026, and fixed in version 2.4.0 released on August 17, 2026.

Community reviews

Loading reviews…