ECDH private-key recovery via unchecked curve points
Published Mar 17, 2026 · Updated Mar 17, 2026
Invalid-curve handling in Stanford Javascript Crypto Library before 1.0.9 allows remote attackers to recover ECDH private keys. The sjcl.ecc.basicKey.publicKey constructor accepts an sjcl.ecc.point object without calling isValid(), and dhJavaEc() exposes the raw x-coordinate of scalar multiplication. The attack requires an application to pass attacker-controlled point objects into ECDH and return deterministic ECDH output; repeated off-curve queries disclose the private scalar.
Summary
What happened
Invalid-curve handling in Stanford Javascript Crypto Library before 1.0.9 allows remote attackers to recover ECDH private keys. The sjcl.ecc.basicKey.publicKey constructor accepts an sjcl.ecc.point object without calling isValid(), and dhJavaEc() exposes the raw x-coordinate of scalar multiplication. The attack requires an application to pass attacker-controlled point objects into ECDH and return deterministic ECDH output; repeated off-curve queries disclose the private scalar.
The record
- CVE
- CVE-2026-4258
- Published
- Mar 17, 2026
- Updated
- Mar 17, 2026
- Vendor
- Stanford University
- Product
- Stanford Javascript Crypto Library
- Classifications
- CWE-347, CWE-325
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 17, 2026CVE publishedPublication date reported by the CVE source.
- Mar 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <*
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- SJCL Invalid Curve Attack proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo