Skip to content
Fencer Vulns
medium 5.6

CVE-2025-14505 json

Elliptic Cryptanalysis vulnerability when `k` has leading zeros

published 2026-01-08 10 mo ago modified 2026-09-10 1 mo ago also EUVD-2026-1445 , GHSA-848j-6mx2-7j84

cvss
5.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

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).

Patch / fix

  • node-elliptic Debian 14 6.6.1+dfsg+~6.4.18-2

debian advisories DEBIAN-CVE-2025-14505

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-14505 updated cvss 5.6

elliptic: Key handling flaws in Elliptic

  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/kibana6-rhel8, openshift-logging/elasticsearch6-rhel9, openshift-logging/logging-curator5-rhel9, openshift-logging/elasticsearch-proxy-rhel9, openshift-logging/elasticsearch-rhel9-operator, openshift-logging/elasticsearch-operator-bundle Red Hat 3scale API Management Platform 2 3scale-amp20/system, 3scale-amp21/system, 3scale-amp22/system, 3scale-amp24/system, 3scale-amp25/system, 3scale-amp26/system, +3 more Red Hat build of Apicurio Registry 2 io.apicurio-apicurio-registry Red Hat Enterprise Linux 8 pcs, grafana, mozjs60, pcs-snmp, grafana-loki, grafana-mssql, +11 more
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Enterprise Linux 9 gjs, pcs, polkit, pcs-snmp, polkit-libs
    affected: workaround, no fix available, no fix planned “Out of support scope”
  • Red Hat Fuse 7 io.apicurio-apicurito, io.syndesis-syndesis-parent Red Hat OpenShift AI (RHOAI) rhoai/odh-data-science-pipelines-argo-argoexec-rhel8, rhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel8 Red Hat OpenShift Container Platform 4 openshift4/ose-console, openshift4/ose-console-rhel9 Red Hat OpenShift Dev Spaces devspaces/code-rhel9, devspaces/code-sshd-rhel9, devspaces/machineexec-rhel9, devspaces-tech-preview/idea-rhel9 Red Hat Process Automation 7 org.uberfire-uberfire-parent, org.kie.workbench-kie-wb-common, org.kie-process-migration-service Red Hat Quay 3 quay/quay-rhel8
    +2 more products
    Red Hat streams for Apache Kafka 2 com.github.streamshub-console Red Hat streams for Apache Kafka 3 com.github.streamshub-console
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
10 mo ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/indutny/elliptic/issues/321 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.6 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
GitHub 3.1 5.6 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
npm elliptic
<=6.6.1
 no fix listed

Affected products

  • N/A Elliptic

Classification

Weakness
  • CWE-1240 Use of a Cryptographic Primitive with a Risky Implementation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.