CVE-2025-15444
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCrypt::Sodium::XS module versions prior to 0.000042, for Perl, include a vulnerable version of libsodium libsodium <= 1.0.20 or a version of libsodium released before December 30, 2025 contains a vulnerability documented as CVE-2025-69277 https://www.cve.org/CVERecord?id=CVE-2025-69277 . The libsodium vulnerability states: In atypical use cases involving certain custom cryptography or untrusted data to crypto_core_ed25519_is_valid_point, mishandles checks for whether an elliptic curve point is valid because it sometimes allows points that aren't in the main cryptographic group. 0.000042 includes a version of libsodium updated to 1.0.20-stable, released January 3, 2026, which includes a fix for the vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Crypt::Sodium::XS Perl module prior to version 0.000042 bundles a vulnerable version of libsodium (≤1.0.20) containing CVE-2025-69277. This vulnerability in the crypto_core_ed25519_is_valid_point function improperly validates elliptic curve points, potentially allowing points outside the main cryptographic group to be accepted. This could undermine Ed25519 cryptographic operations that rely on point validity checks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.000042CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Crypt::Sodium::XS is installedRun: perl -MCrypt::Sodium::XS -e 'print $Crypt::Sodium::XS::VERSION . "\n"' 2>/dev/null || echo 'Not installed'Affected if The module is installed and version is less than 0.000042
-
Check installed Crypt::Sodium::XS version via cpanRun: cpan -D Crypt::Sodium::XS 2>/dev/null | grep -i versionAffected if Version listed is less than 0.000042
-
Verify Ed25519 key operations are in useSearch codebase for Ed25519-related function calls such as crypto_sign_seed_keypair, crypto_sign_keypair, crypto_sign, crypto_sign_open, or crypto_core_ed25519_is_valid_pointAffected if Ed25519 cryptographic operations are performed using this module on untrusted input
-
Check if application processes external Ed25519 public keysReview application logic for code paths that accept, validate, or verify Ed25519 points from untrusted sources such as user input, network data, or filesAffected if The application validates or uses Ed25519 points from untrusted or external sources
You are affected if Crypt::Sodium::XS version is below 0.000042 AND your code performs Ed25519 point validation or cryptographic operations on untrusted input using this module.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.000042
Upgrade Crypt::Sodium::XS to version 0.000042 or later which includes libsodium 1.0.20-stable containing the fixed version. For applications using custom cryptography or processing untrusted data with Ed25519, verify point validation behavior after the update.
Crypt::Sodium::XS version 0.000042 (which includes libsodium 1.0.20-stable)
- Check current installed version of Crypt::Sodium::XS by running: perl -MCrypt::Sodium::XS -e 'print $Crypt::Sodium::XS::VERSION'
- Upgrade Crypt::Sodium::XS to version 0.000042 using your Perl module installer, for example: cpan -T Crypt::Sodium::XS or cpanm Crypt::Sodium::[email protected]
- Verify the upgrade was successful by re-running: perl -MCrypt::Sodium::XS -e 'print $Crypt::Sodium::XS::VERSION'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15444 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-15444 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data