MediumGHSA-mrfv-m5wm-5w6wCVE-2025-69277PYSEC-2026-1448PYSEC-2026-3002

libsodium has Incomplete List of Disallowed Inputs

Published 31 Dec 2025 · Updated 10 Sept 2026

Is your project on an affected paragonie/sodium_compat?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=2 <2.5.0
Fixed in
2.5.0
Update to the fixed version for your release line, for example:composer require paragonie/sodium_compat:^2.5.0
Affected
<1.24.0
Fixed in
1.24.0
Update to the fixed version for your release line, for example:composer require paragonie/sodium_compat:^1.24.0
pynaclPyPI
Affected
<1.6.2
Fixed in
1.6.2
Update to the fixed version for your release line, for example:pip install 'pynacl>=1.6.2'
Affected
<3.6.1
Fixed in
3.6.1
Update to the fixed version for your release line, for example:pip install 'hdwallet>=3.6.1'

Details

libsodium before ad3004e, 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.

This advisoory lists packages in the GitHub Advisory Database's supported ecosystems that are affected by this vulnerability due to a vulnerable dependency.

Is GHSA-mrfv-m5wm-5w6w in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected paragonie/sodium_compat, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.