Cryptographic validation bypass via incomplete subgroup check
Published Jan 6, 2026 · Updated Jan 6, 2026
Cryptographic validation bypass in Crypt::Sodium::XS before 0.000042 allows remote attackers to pass invalid Ed25519 points as valid. The bundled libsodium subgroup check in ge25519_is_on_main_subgroup multiplies a point by L but tests only X=0, omitting the required Y=Z identity condition. Exposure requires custom cryptography that passes untrusted points to core_ed25519_is_valid_point; high-level signature APIs are unaffected.
Summary
What happened
Cryptographic validation bypass in Crypt::Sodium::XS before 0.000042 allows remote attackers to pass invalid Ed25519 points as valid. The bundled libsodium subgroup check in ge25519_is_on_main_subgroup multiplies a point by L but tests only X=0, omitting the required Y=Z identity condition. Exposure requires custom cryptography that passes untrusted points to core_ed25519_is_valid_point; high-level signature APIs are unaffected.
The record
- CVE
- CVE-2025-15444
- Published
- Jan 6, 2026
- Updated
- Jan 6, 2026
- Vendor
- Brad Barden
- Product
- Crypt::Sodium::XS
- Classifications
- CWE-347
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 6, 2026CVE publishedPublication date reported by the CVE source.
- Jan 6, 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 <0.000042
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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