GHSA-w54x-xfxg-4gxq is a medium-severity (CVSS 5.3) CWE-522 vulnerability in github.com/neuvector/neuvector. O3 Security confirms whether GHSA-w54x-xfxg-4gxq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
NeuVector process with sensitive arguments lead to leakage
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
When a Java command with password parameters is executed and terminated by NeuVector for Process rule violation. For example,
java -cp /app ... Djavax.net.ssl.trustStorePassword=<Password>
The command with the password appears in the NeuVector security event. To prevent this, NeuVector uses the following default regular expression to detect and redact sensitive data from process commands:
(?i)(password|passwd|token)
Also, you can define custom patterns to redact by creating a Kubernetes ConfigMap. For example:
kubectl create configmap neuvector-custom-rules --from-file=secret-patterns.yaml -n neuvector
Sample secret-patterns.yaml content:
Pattern_list:
- (?i)(pawd|pword)
- (?i)(secret)
NeuVector uses the default and custom regex to decide whether the process command in a security event should be redacted.
Note: If numerous regular expression (regex) patterns are configured in the Kubernetes ConfigMap for extended coverage of sensitive data matching, it can significantly impact performance of NeuVector enforcer, particularly in scenarios involving large inputs or frequent execution. The primary factor contributing to performance issues in regex is backtracking, where the regex engine attempts various matching paths when a pattern doesn't immediately find a match.
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-20250902144615-f9ddbdf42031 |
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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/neuvector/neuvector to 0.0.0-20250902144615-f9ddbdf42031 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w54x-xfxg-4gxq 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 pinpoints whether GHSA-w54x-xfxg-4gxq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-w54x-xfxg-4gxq. 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-w54x-xfxg-4gxq in your dependencies?
O3 detects GHSA-w54x-xfxg-4gxq across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.