CVE-2025-54467: NeuVector process with sensitive arguments lead to leakage
Impact When a Java command with password parameters is executed and terminated by NeuVector for Process rule violation. For example, 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: Also, you can define custom patterns to redact by creating a Kubernetes ConfigMap.
Published Aug 28, 2025 · Updated Jul 2, 2026
Affected packages
github.com/neuvector/neuvector
- Ecosystem
- Go
- Affected
- < 0.0.0-20250902144615-f9ddbdf42031
- Fixed in
- 0.0.0-20250902144615-f9ddbdf42031
- Check
go list -m github.com/neuvector/neuvector
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 neuvectorSample 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.
Credited to holyspectral.
References
- https://github.com/neuvector/neuvector/security/advisories/GHSA-w54x-xfxg-4gxq
- https://nvd.nist.gov/vuln/detail/CVE-2025-54467
- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-54467
- https://github.com/neuvector/neuvector/commit/f9ddbdf420319cede3c490c1de03f48d953896ae
- https://github.com/advisories/GHSA-w54x-xfxg-4gxq
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2025-66001
NeuVector OpenID Connect is vulnerable to man-in-the-middle (MITM)
high8.8Dec 12, 2025CVE-2025-54469
NeuVector Enforcer is vulnerable to Command Injection and Buffer overflow
critical9.9Oct 21, 2025CVE-2025-54470
NeuVector telemetry sender is vulnerable to MITM and DoS
high8.6Oct 21, 2025CVE-2025-54471
NeuVector is shipping cryptographic material into its binary
medium6.5Oct 21, 2025CVE-2025-53884
NeuVector has an insecure password storage and is vulnerable to rainbow attack
medium5.3Aug 28, 2025CVE-2025-8077
NeuVector admin account has insecure default password
critical9.8Aug 28, 2025
