GHSA-mrfv-m5wm-5w6w 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
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 GHSA-mrfv-m5wm-5w6w.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-mrfv-m5wm-5w6w plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,238 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | paragonie/sodium_compat | ≥ 2&&< 2.5.0 | 2.5.0composer require paragonie/sodium_compat:^2.5.0 |
| 🐘Packagist | paragonie/sodium_compat | all versions | 1.24.0composer require paragonie/sodium_compat:^1.24.0 |
| 🐍PyPI | pynacl | all versions | 1.6.2pip install --upgrade 'pynacl==1.6.2' |
| 🐍PyPI | hdwallet | all versions | 3.6.1pip install --upgrade 'hdwallet==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, 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 GHSA-mrfv-m5wm-5w6w 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mrfv-m5wm-5w6w can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mrfv-m5wm-5w6w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Hardened Images | libsodium-main-1.0.22-1.hum1 | RHSA-2026:7369 |
Frequently Asked Questions
Is GHSA-mrfv-m5wm-5w6w in your dependencies?
O3 Security finds GHSA-mrfv-m5wm-5w6w across Packagist, PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.