CVE-2025-53884

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.

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.

CVE-2025-53884 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-20250825191744-da1a462074c3); 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-53884? CVE-2025-53884 is a medium-severity security vulnerability in github.com/neuvector/neuvector (go), affecting versions < 0.0.0-20250825191744-da1a462074c3. It is fixed in 0.0.0-20250825191744-da1a462074c3.
2. How severe is CVE-2025-53884? CVE-2025-53884 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-53884? github.com/neuvector/neuvector (go) versions < 0.0.0-20250825191744-da1a462074c3 is affected.
4. Is there a fix for CVE-2025-53884? Yes. CVE-2025-53884 is fixed in 0.0.0-20250825191744-da1a462074c3. Upgrade to this version or later.
5. Is CVE-2025-53884 exploitable, and should I be worried? Whether CVE-2025-53884 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-53884 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-53884? Upgrade github.com/neuvector/neuvector to 0.0.0-20250825191744-da1a462074c3 or later.