CVE-2025-15444
CRITICAL flaw in Crypt::Sodium::XS/libsodium Ed25519 point validation.
Is CVE-2025-15444 being exploited?
Not confirmed. CVE-2025-15444 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.
How severe is CVE-2025-15444?
CVE-2025-15444 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-15444?
Yes. A fix has been recorded for CVE-2025-15444. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-15444 affect?
CVE-2025-15444 affects Crypt::Sodium::XS < 0.000042, libsodium <= 1.0.20, Perl applications using these libsodium versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-15444?
Upgrade to Crypt::Sodium::XS 0.000042+ and libsodium 1.0.20-stable
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Invalid EC point validation may allow forged signatures or validation bypass in affected apps.
Patch when possible
- affected< 0.000042
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.