CVE-2022-41340 is a high-severity (CVSS 7.5) CWE-347 vulnerability in @lionello/secp256k1-js. A fix is available for @lionello/secp256k1-js — see the affected versions and patch details below.
secp256k1-js implements ECDSA without required r and s validation, leading to signature forgery
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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 CVE-2022-41340.
EPSS Exploitation Probability
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
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.
@lionello/secp256k1-jsnpmDescription
The secp256k1-js package before 1.1.0 for Node.js implements ECDSA without required r and s validation, leading to signature forgery.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @lionello/secp256k1-js | all versions | 1.1.0npm install @lionello/secp256k1-js@1.1.0 |
Affected Products
secp256k1-jssecp256k1-js_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @lionello/secp256k1-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @lionello/secp256k1-js to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41340 is resolved across your whole dependency graph.
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.
Frequently Asked Questions
Is CVE-2022-41340 in your dependencies?
Find it across npm, including transitive dependencies.