PatchTheCVECVE-2022-41340: The secp256k1-js package before 1.1.0 for Node.js implements ECDSA without required r and s validation, leadin
CVE-2022-41340 is a high-severity flaw (CVSS 7.5) affecting secp256k1-js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The secp256k1-js package before 1.1.0 for Node.js implements ECDSA without required r and s validation, leading to signature forgery.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.7% (top 47%) |
| CISA exploited list | No |
| Weakness | CWE-347 |
| Published | 2022-09-24 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-41340?
secp256k1-js: upgrade to 1.1.0. Exact commands for each OS are on this page.
Is CVE-2022-41340 being exploited?
CVE-2022-41340 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-41340 affect?
CVE-2022-41340 affects secp256k1-js. Severity is high (CVSS 7.5). The secp256k1-js package before 1.1.0 for Node.js implements ECDSA without required r and s validation, leading to signature forgery.
How urgent is CVE-2022-41340?
Priority 45/100. High severity; Remotely exploitable, no login, no user action