GHSA-7g9j-g5jg-3vv3 is a low-severity (CVSS 3.1) CWE-642 vulnerability in snow. A fix is available for snow — see the affected versions and patch details below.
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-7g9j-g5jg-3vv3.
EPSS Exploitation Probability
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
snowReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Impact
There was a logic bug where unauthenticated payloads could still cause a nonce increment in snow's internal state. For an attacker with the ability to inject packets into the channel Noise is talking over, this allows a denial-of-service type attack which could prevent communication as it causes the sending and receiving side to be expecting different nonce values than would arrive.
Note that this only affects those who are using the stateful TransportState, not those using StatelessTransportState.
Patches
This has been patched in version 0.9.5, and all users are recommended to update.
References
There will be a more formal report of this in the near future.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | snow | all versions | 0.9.5cargo update -p snow --precise 0.9.5 |
Affected Products
snowmcgintyDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for snow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update snow to 0.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7g9j-g5jg-3vv3 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.
Frequently Asked Questions
Is GHSA-7g9j-g5jg-3vv3 in your dependencies?
Find it across crates.io, including transitive dependencies.