CVE-2025-54467

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.

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.

CVE-2025-54467 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20250902144615-f9ddbdf42031); upgrading removes the vulnerable code path.

Kodem intelligence

This issue is fixed in NeuVector version 5.4.6 and later.

1. What is CVE-2025-54467? CVE-2025-54467 is a medium-severity security vulnerability in github.com/neuvector/neuvector (go), affecting versions < 0.0.0-20250902144615-f9ddbdf42031. It is fixed in 0.0.0-20250902144615-f9ddbdf42031.
2. How severe is CVE-2025-54467? CVE-2025-54467 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/neuvector/neuvector are affected by CVE-2025-54467? github.com/neuvector/neuvector (go) versions < 0.0.0-20250902144615-f9ddbdf42031 is affected.
4. Is there a fix for CVE-2025-54467? Yes. CVE-2025-54467 is fixed in 0.0.0-20250902144615-f9ddbdf42031. Upgrade to this version or later.
5. Is CVE-2025-54467 exploitable, and should I be worried? Whether CVE-2025-54467 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-54467 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-54467? Upgrade github.com/neuvector/neuvector to 0.0.0-20250902144615-f9ddbdf42031 or later.