CVE-2025-15444: Crypt::Sodium::XS module versions prior to 0.000042, for Perl, include a vulnerable version of libsodium
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: azl3 libsodium 1.0.19-1 on Azure Linux 3.0 1.0.19-2; azl3 libsodium 1.0.19-2 on Azure Linux 3.0 1.0.19-2; cbl2 libsodium 1.0.18-6 on CBL Mariner 2.0 1.0.18-7.
Low priority for now. Upgrade to azl3 libsodium 1.0.19-1 on Azure Linux 3.0 1.0.19-2; azl3 libsodium 1.0.19-2 on Azure Linux 3.0 1.0.19-2; cbl2 libsodium 1.0.18-6 on CBL Mariner 2.0 1.0.18-7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Crypt::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.
- Published
- Jan 6, 2026
- Updated
- Oct 7, 2026
- EPSS
- 0.2% · 19th percentile
- CWE
- CWE-347
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| iamb | crypt::sodium::xs | cpe:2.3:a:iamb:crypt::sodium::xs |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CPANSec). Independent of NVD's CPE analysis and usually ahead of it.
IAMB Crypt::Sodium::XS
- before 0.000042affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- iamb crypt::sodium::xsbefore 0.000042
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.6 | libsodium | before 1.0.18-150000.4.11.1 | 1.0.18-150000.4.11.1 |
| openSUSE:Leap 15.6 | libsodium | before 1.0.18-150000.4.14.1 | 1.0.18-150000.4.14.1 |
| openSUSE:Leap 16.0 | libsodium | before 1.0.20-160000.3.1 | 1.0.20-160000.3.1 |
| openSUSE:Tumbleweed | libsodium | before 1.0.21-1.1 | 1.0.21-1.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | dnsdist | before 1.8.0-150400.9.8.1 | 1.8.0-150400.9.8.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | usbguard | before 1.1.2-150400.3.5.1 | 1.1.2-150400.3.5.1 |
| SUSE:Linux Enterprise Micro 5.3 | libsodium | before 1.0.22-150000.4.17.1 | 1.0.22-150000.4.17.1 |
| SUSE:Linux Enterprise Micro 5.3 | libsodium | before 1.0.18-150000.4.11.1 | 1.0.18-150000.4.11.1 |
| SUSE:Linux Enterprise Micro 5.3 | libsodium | before 1.0.18-150000.4.14.1 | 1.0.18-150000.4.14.1 |
| SUSE:Linux Enterprise Micro 5.3 | zeromq | before 4.2.3-150000.3.17.1 | 4.2.3-150000.3.17.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | dnsdist | before 1.9.12-150700.3.11.2 | 1.9.12-150700.3.11.2 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | unbound | before 1.25.2-150600.23.21.4 | 1.25.2-150600.23.21.4 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | usbguard | before 1.1.2-150500.6.2.2 | 1.1.2-150500.6.2.2 |
| SUSE:Linux Enterprise Module for Legacy 15 SP7 | apache2-mod_php7 | before 7.4.33-150400.4.75.1 | 7.4.33-150400.4.75.1 |
| SUSE:Linux Enterprise Module for Legacy 15 SP7 | php7 | before 7.4.33-150400.4.75.2 | 7.4.33-150400.4.75.2 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | php7-embed | before 7.4.33-150400.4.75.1 | 7.4.33-150400.4.75.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | php7-fastcgi | before 7.4.33-150400.4.75.1 | 7.4.33-150400.4.75.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | php7-fpm | before 7.4.33-150400.4.75.1 | 7.4.33-150400.4.75.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | php7-test | before 7.4.33-150400.4.75.1 | 7.4.33-150400.4.75.1 |
| SUSE:Linux Enterprise Module for Public Cloud 12 | libsodium | before 1.0.16-1.12.1 | 1.0.16-1.12.1 |
| SUSE:Linux Enterprise Module for Public Cloud 12 | libsodium | before 1.0.16-1.15.1 | 1.0.16-1.15.1 |
| SUSE:Linux Micro 6.0 | libsodium | before 1.0.18-5.1 | 1.0.18-5.1 |
| SUSE:Linux Micro 6.0 | libsodium | before 1.0.18-4.1 | 1.0.18-4.1 |
| SUSE:Linux Micro 6.1 | libsodium | before 1.0.18-slfo.1.1_3.1 | 1.0.18-slfo.1.1_3.1 |
+2
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 libsodium 1.0.19-1 on Azure Linux 3.0 | 1.0.19-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 libsodium 1.0.19-2 on Azure Linux 3.0 | 1.0.19-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 libsodium 1.0.18-6 on CBL Mariner 2.0 | 1.0.18-7 · CBL-Mariner Releases | Microsoft (MSRC) |
| opensuse:libsodium | 1.0.18-150000.4.11.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:apache2-mod_php7 | 7.4.33-150400.4.75.1 · SUSE:Linux Enterprise Module for Legacy 15 SP7 | Package registry (OSV) |
| suse:dnsdist | 1.9.12-150700.3.11.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:libsodium | 1.0.16-1.12.1 · SUSE:Linux Enterprise Module for Public Cloud 12 | Package registry (OSV) |
| suse:libsodium | 1.0.18-150000.4.11.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:php7 | 7.4.33-150400.4.75.2 · SUSE:Linux Enterprise Module for Legacy 15 SP7 | Package registry (OSV) |
| suse:php7-embed | 7.4.33-150400.4.75.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | Package registry (OSV) |
| suse:php7-fastcgi | 7.4.33-150400.4.75.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | Package registry (OSV) |
| suse:php7-fpm | 7.4.33-150400.4.75.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | Package registry (OSV) |
| suse:php7-test | 7.4.33-150400.4.75.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | Package registry (OSV) |
| suse:unbound | 1.25.2-150600.23.21.4 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:usbguard | 1.1.2-150500.6.2.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:zeromq | 4.2.3-150000.3.17.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.