How severe is CVE-2025-69277?

CVE-2025-69277 has a CVSS score of 4.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-69277?

CVE-2025-69277 affects the following packages: paragonie/sodium_compat (Packagist), paragonie/sodium_compat (Packagist), pynacl (PyPI), hdwallet (PyPI). Ecosystems affected: Packagist, PyPI.

How do I fix CVE-2025-69277?

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.

How do I detect CVE-2025-69277 in my Packagist, PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for paragonie/sodium_compat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-69277 if there is no patch (or I can't update yet)?

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.

Is CVE-2025-69277 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-69277 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-69277?

CVE-2025-69277 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-69277?

CVE-2025-69277 is classified as CWE-184 (CWE-184). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-69277 published, and has it been updated?

CVE-2025-69277 was published on December 31, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2025-69277 — sodium_compat

MEDIUMFix: jedisct1/libsodium@ad3004e

CVE-2025-69277 is a medium-severity (CVSS 4.5) CWE-184 vulnerability in paragonie/sodium_compat. A fix is available for paragonie/sodium_compat — see the affected versions and patch details below.

libsodium has Incomplete List of Disallowed Inputs

Also known asGHSA-mrfv-m5wm-5w6wPYSEC-2026-1448PYSEC-2026-3002

Published

Dec 31, 2025

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-69277.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐘paragonie/sodium_compat🐘paragonie/sodium_compat🐍pynacl🐍hdwallet

Real-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

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

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`paragonie/sodium_compat`	≥ 2&&< 2.5.0	2.5.0`composer require paragonie/sodium_compat:^2.5.0`
🐘Packagist	`paragonie/sodium_compat`	all versions	1.24.0`composer require paragonie/sodium_compat:^1.24.0`
🐍PyPI	`pynacl`	all versions	1.6.2`pip install --upgrade 'pynacl==1.6.2'`
🐍PyPI	`hdwallet`	all versions	3.6.1`pip install --upgrade 'hdwallet==3.6.1'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for paragonie/sodium_compat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability is rated Moderate for Red Hat products as it primarily affects atypical use cases involving custom cryptographic implementations or untrusted data processing with `crypto_core_ed25519_is_valid_point`. Standard libsodium deployments are not expected to be impacted by this flaw.

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for CVE-2025-69277 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Hardened Images	`libsodium-main-1.0.22-1.hum1`	RHSA-2026:7369

Frequently Asked Questions

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](https://github.com/github/advisory-database?tab=readme-ov-file#supported-ecosystems) that are affected by this vulnerability due to a vulnerable dependency.

O3 Security · Impact-Aware SCA

Is CVE-2025-69277 in your dependencies?

Find it across Packagist, PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works