Is paragonie/sodium_compat 1.16 vulnerable?
Composer · 2 releases from 1.16.0 to 1.16.1 · latest paragonie/sodium_compat is 2.5.2 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. paragonie/sodium_compat 1.16.1, the last 1.16 release, is affected by 1 known security advisory (1 medium), including CVE-2025-69277. Upgrade to 1.24.0 or later to fix all of them.
composer require paragonie/sodium_compat:^1.24.0Is your project on an affected paragonie/sodium_compat?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting paragonie/sodium_compat 1.16.1
libsodium has Incomplete List of Disallowed Inputs
- Affected
- >=2 <2.5.0 · <1.24.0
- Fixed in
- 1.24.0, 2.5.0
Every paragonie/sodium_compat 1.16.x release
Affected: 1.16.0 to 1.16.1. Latest paragonie/sodium_compat: 2.5.2.
| Version | Known advisories |
|---|---|
| paragonie/sodium_compat 1.16.1 | CVE-2025-69277 |
| paragonie/sodium_compat 1.16.0 | CVE-2025-69277 |
Which of your client projects are still on paragonie/sodium_compat 1.16?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact paragonie/sodium_compat version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other paragonie/sodium_compat versions
- paragonie/sodium_compat 1.19
- paragonie/sodium_compat 1.18
- paragonie/sodium_compat 1.17
- paragonie/sodium_compat 1.15
- paragonie/sodium_compat 1.14
- paragonie/sodium_compat 1.13
- paragonie/sodium_compat 2.5
- paragonie/sodium_compat 2.4
- paragonie/sodium_compat 2.3
- paragonie/sodium_compat 2.2
- paragonie/sodium_compat 2.1
- paragonie/sodium_compat 2.0
- All paragonie/sodium_compat advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.