CVE-2025-69277
MEDIUMCVE-2025-69277 is a medium-severity (CVSS 4.5) CWE-184 vulnerability in paragonie/sodium_compat. O3 Security confirms whether CVE-2025-69277 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
libsodium has Incomplete List of Disallowed Inputs
Blast Radius
paragonie/sodium_compat🐘paragonie/sodium_compat🐍pynacl🐍hdwalletReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist, PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | paragonie/sodium_compat | ≥ 2&&< 2.5.0 | 2.5.0 |
| 🐘Packagist | paragonie/sodium_compat | all versions | 1.24.0 |
| 🐍PyPI | pynacl | all versions | 1.6.2 |
| 🐍PyPI | hdwallet | all versions | 3.6.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for paragonie/sodium_compat. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update paragonie/sodium_compat to 2.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-69277 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-69277 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-69277. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-69277 in your dependencies?
O3 detects CVE-2025-69277 across Packagist, PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.