Skip to main content
No exploitation reportedFix available

CVE-2025-14505

Elliptic Cryptanalysis vulnerability when `k` has leading zeros

No exploitation reported by the sources we read.

  • Published2026-01-08
  • WeaknessCWE-1240

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of 'k' (as computed based on step 3.2 of RFC 6979 https://datatracker.ietf.org/doc/html/rfc6979 ) has leading zeros and is susceptible to cryptanalysis, which can lead to secret key exposure. This happens, because the byte-length of 'k' is incorrectly computed, resulting in its getting truncated during the computation. Legitimate transactions or communications will be broken as a result. Furthermore, due to the nature of the fault, attackers could–under certain conditions–derive the secret key, if they could get their hands on both a faulty signature generated by a vulnerable version of Elliptic and a correct signature for the same inputs. This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).

Timeline

dates in UTC
  1. 2026-01-0821:15CVE publishedNVD

Versions per branch

OSV
elliptic
BranchAffectedFixed in
6.6≤ 6.6.1no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As HeroDevs, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-01-08

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • commercial-gitlab-rails-ee-19.1Chainguardall versions · fixed in 19.1.7-r3
  • commercial-gitlab-rails-ee-19.2Chainguardall versions · fixed in 19.2.7-r1and 1 other package
  • commercial-gitlab-rails-ee-19.3Chainguardall versions · fixed in 19.3.3-r1and 1 other package
  • commercial-gitlab-rails-ee-19.4Chainguardall versions · fixed in 19.4.1-r1and 1 other package
  • ellipticTuxCare:npmfrom 6.6.1-tuxcare.0 · fixed in 6.6.1-tuxcare.1
  • ellipticTuxCare:npmfrom 6.4.1-tuxcare.0 · fixed in 6.4.1-tuxcare.1
  • ellipticTuxCare:npmfrom 6.5.4-tuxcare.0 · fixed in 6.5.4-tuxcare.1
  • ellipticTuxCare:npmfrom 6.5.5-tuxcare.0 · fixed in 6.5.5-tuxcare.1

30 more package ranges on OSV.dev

Vendor advisories

  • CVE-2025-14505 Red Hat Product Security62 known affected

    elliptic: Key handling flaws in Elliptic

    openshift-logging/elasticsearch-operator-bundle as a component of Logging Subsystem for Red Hat OpenShift · openshift-logging/elasticsearch-proxy-rhel9 as a component of Logging Subsystem for Red Hat OpenShift · openshift-logging/elasticsearch-rhel9-operator as a component of Logging Subsystem for Red Hat OpenShift · +59 more

Full record on NVD

Fix

  1. Workaround from the vendor Red Hat Product Security CVE-2025-14505 · 62 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
  2. No fix available, says the vendor Red Hat Product Security CVE-2025-14505 · 59 productsFix deferred
  3. No fix planned, says the vendor Red Hat Product Security CVE-2025-14505 · 3 productsOut of support scope

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2026-01-08
  • CNACVSS 3.15.6known since 2026-10-23
  • CNAweakness (CWE)CWE-1240known since 2026-10-23
  • FIRST EPSSEPSS score0.2 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryLOW2026-01-09

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
Published
2026-01-08
Last Modified
2026-06-17
NVD status
Deferred
GitHub Advisory
GHSA-848j-6mx2-7j84

Frequently asked questions

What is CVE-2025-14505?

The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of 'k' (as computed based on step 3.2 of RFC 6979 https://datatracker.ietf.org/doc/html/rfc6979 ) has leading zeros and is susceptible to cryptanalysis, which can lead to secret key exposure. This happens, because the byte-length of 'k' is incorrectly computed, resulting in its getting truncated during the computation. Legitimate transactions or communications will be broken as a result. Furthermore, due to the nature of the fault, attackers could–under certain conditions–derive the secret key, if they could get their hands on both a faulty signature generated by a vulnerable version of Elliptic and a correct signature for the same inputs. This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).

Is CVE-2025-14505 actively exploited?

Active exploitation of CVE-2025-14505 has not been confirmed. Its EPSS score was 0.2% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-14505?

CVE-2025-14505 has a CVSS v3 base score of 5.6 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L.

Running elliptic? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record