Summary
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.
Impact
CVE-2025-69277 has a CVSS score of 4.5 (Medium). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.5.0, 1.24.0, 1.6.2, 3.6.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
paragonie/sodium_compat to 2.5.0 or later; paragonie/sodium_compat to 1.24.0 or later; PyNaCl to 1.6.2 or later; hdwallet to 3.6.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-69277? CVE-2025-69277 is a medium-severity security vulnerability in paragonie/sodium_compat (composer), affecting versions >= 2, < 2.5.0. It is fixed in 2.5.0, 1.24.0, 1.6.2, 3.6.1.
- How severe is CVE-2025-69277? CVE-2025-69277 has a CVSS score of 4.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2025-69277?
paragonie/sodium_compat(composer) (versions >= 2, < 2.5.0)PyNaCl(pip) (versions < 1.6.2)hdwallet(pip) (versions < 3.6.1)
- Is there a fix for CVE-2025-69277? Yes. CVE-2025-69277 is fixed in 2.5.0, 1.24.0, 1.6.2, 3.6.1. Upgrade to this version or later.
- Is CVE-2025-69277 exploitable, and should I be worried? Whether CVE-2025-69277 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-69277 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-69277?
- Upgrade
paragonie/sodium_compatto 2.5.0 or later - Upgrade
paragonie/sodium_compatto 1.24.0 or later - Upgrade
PyNaClto 1.6.2 or later - Upgrade
hdwalletto 3.6.1 or later
- Upgrade