NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Elliptic's verify function omits uniqueness validationGHSA-434g-2637-qmqr

MEDIUMFix: indutny/elliptic@7ac5360

GHSA-434g-2637-qmqr is a medium-severity (CVSS 5.3) CWE-347 vulnerability in elliptic. A fix is available for elliptic — see the affected versions and patch details below.

Also known asCVE-2024-48949
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-434g-2637-qmqr.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk
0.00%0.34%0.67%1.01%0.3%0.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

3Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
ellipticnpm
16.6Mdownloads / week

Description

The Elliptic package 6.5.5 for Node.js for EDDSA implementation does not perform the required check if the signature proof(s) is within the bounds of the order n of the base point of the elliptic curve, leading to signature malleability. Namely, the verify function in lib/elliptic/eddsa/index.js omits sig.S().gte(sig.eddsa.curve.n) || sig.S().isNeg() validation.

This vulnerability could have a security-relevant impact if an application relies on the uniqueness of a signature.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmellipticall versions6.5.6npm install elliptic@6.5.6

Affected Products

1 product · 1 configurations
Application
ellipticindutny
< 6.5.6
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for elliptic, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update elliptic to 6.5.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-434g-2637-qmqr is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Thunderbird is not supported in Red Hat Enterprise Linux 7 ELS.

Workaround published by Red Hat
Mitigation 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.
Source: Red Hat security advisory for GHSA-434g-2637-qmqr (CC BY 4.0)
ProductFixed inAdvisory
multicluster engine for Kubernetes 2.4 for RHEL 8multicluster-engine/addon-manager-rhel8:v2.4.6-12RHSA-2024:8533
multicluster engine for Kubernetes 2.5 for RHEL 9multicluster-engine/console-mce-rhel9:v2.5.7-3RHSA-2024:6738
Red Hat Advanced Cluster Management for Kubernetes 2.10 for RHEL 9rhacm2/console-rhel9:v2.10.6-3RHSA-2024:6779
Red Hat Advanced Cluster Management for Kubernetes 2.11 for RHEL 9rhacm2/acm-cluster-permission-rhel9:v2.11.3-4RHSA-2024:7994
Red Hat Advanced Cluster Management for Kubernetes 2.12 for RHEL 9rhacm2/acm-cli-rhel9:v2.12.0-17RHSA-2024:8974
Red Hat Advanced Cluster Management for Kubernetes 2.9 for RHEL 8rhacm2/acm-cluster-permission-rhel8:v2.9.5-9RHSA-2024:8546
Red Hat Enterprise Linux 8.2 Advanced Update Supportgrafana-0:6.3.6-6.el8_2RHSA-2024:8507
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Supportgrafana-0:7.3.6-8.el8_4RHSA-2024:8351

Frequently Asked Questions

The Elliptic package 6.5.5 for Node.js for EDDSA implementation does not perform the required check if the signature proof(s) is within the bounds of the order n of the base point of the elliptic curve, leading to signature malleability. Namely, the `verify` function in `lib/elliptic/eddsa/index.js` omits `sig.S().gte(sig.eddsa.curve.n) || sig.S().isNeg()` validation. This vulnerability could have a security-relevant impact if an application relies on the uniqueness of a signature.
O3 Security · Impact-Aware SCA

Is GHSA-434g-2637-qmqr in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Elliptic's verify function omits uniqueness validation