CVE-2025-67860

NeuVector scanner insecurely handles passwords as command arguments

Workarounds

There is no workaround for this issue. Users are recommended to upgrade, as soon as possible, to a version of NeuVector scanner that contains the fix.

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.

A vulnerability has been identified in the NeuVector scanner where the scanner process accepts registry and controller credentials as command-line arguments, potentially exposing sensitive credentials to local users. This may allow unauthorized access to registries or the NeuVector controller, potentially enabling image manipulation, information disclosure, or further lateral movement within the environment.

Important:

• For the exposure of credentials not related to Rancher NeuVector, the final impact severity for confidentiality, integrity and availability is dependent on the permissions the leaked credentials have on their services.
• It is recommended to review for potentially leaked credentials in this scenario and to change them if deemed necessary.

Please consult the associated MITRE ATT&CK, Technique, Credential Access and Unsecured Credentials for further information about this category of attack.

CVE-2025-67860 has a CVSS score of 3.8 (Low). The vector is requires local access, low 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 (4.072); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Patched versions include release v4.072 and above.

Starting from version v4.072, the scanner monitor process does not pass credentials to the scanner anymore. Instead, scanner process gets credentials information from environment variables, preventing them from being exposed through /proc/*/cmdline.

1. What is CVE-2025-67860? CVE-2025-67860 is a low-severity security vulnerability in github.com/neuvector/scanner (go), affecting versions >= 4.0, < 4.072. It is fixed in 4.072.
2. How severe is CVE-2025-67860? CVE-2025-67860 has a CVSS score of 3.8 (Low). 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/scanner are affected by CVE-2025-67860? github.com/neuvector/scanner (go) versions >= 4.0, < 4.072 is affected.
4. Is there a fix for CVE-2025-67860? Yes. CVE-2025-67860 is fixed in 4.072. Upgrade to this version or later.
5. Is CVE-2025-67860 exploitable, and should I be worried? Whether CVE-2025-67860 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-67860 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-67860? Upgrade github.com/neuvector/scanner to 4.072 or later.