GHSA-8ff6-pc43-jwv3 is a medium-severity (CVSS 5.3) CWE-759 vulnerability in github.com/neuvector/neuvector. A fix is available for github.com/neuvector/neuvector — see the affected versions and patch details below.
NeuVector has an insecure password storage and is vulnerable to rainbow attack
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-8ff6-pc43-jwv3.
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-8ff6-pc43-jwv3 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,636 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
github.com/neuvector/neuvectorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
NeuVector stores user passwords and API keys using a simple, unsalted hash. This method is vulnerable to rainbow table attack (offline attack where hashes of known passwords are precomputed).
NeuVector generates a cryptographically secure, random 16-character salt and uses it with the PBKDF2 algorithm to create the hash value for the following actions:
- Creating a user
- Updating a user’s password
- Creating an API key
Note: After upgrading to NeuVector 5.4.6, users must log in again so that NeuVector can regenerate the password hash. For API keys, you must send at least one request per API key to regenerate its hash value.
Patches
This issue is fixed in NeuVector version 5.4.6 and later.
Workarounds
There is no workaround. Upgrade to a patched version of NeuVector as soon as possible.
References
If you have any questions or comments about this advisory:
- Reach out to the SUSE Rancher Security team for security related inquiries.
- Open an issue in the NeuVector repository.
- Verify with our support matrix and product support lifecycle.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/neuvector/neuvector | all versions | 0.0.0-20250825191744-da1a462074c3go get github.com/neuvector/neuvector@v0.0.0-20250825191744-da1a462074c3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/neuvector/neuvector, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/neuvector/neuvector to 0.0.0-20250825191744-da1a462074c3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8ff6-pc43-jwv3 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-8ff6-pc43-jwv3 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-8ff6-pc43-jwv3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8ff6-pc43-jwv3 in your dependencies?
O3 Security finds GHSA-8ff6-pc43-jwv3 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.