Summary
Workarounds
If you cannot update to a patched version, you can temporarily disable the Report anonymous cluster data, which is enabled by default in NeuVector.
To change this setting, go to Settings → Configuration → Report anonymous cluster data in the NeuVector UI.
Disabling this option prevents NeuVector from sending telemetry data to the telemetry server, which helps mitigate this vulnerability.
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.
Impact
This vulnerability affects NeuVector deployments only when the Report anonymous cluster data option is enabled. When this option is enabled, NeuVector sends anonymous telemetry data to the telemetry server at https://upgrades.neuvector-upgrade-responder.livestock.rancher.io.
In affected versions, NeuVector does not enforce TLS certificate verification when transmitting anonymous cluster data to the telemetry server. As a result, the communication channel is susceptible to man-in-the-middle (MITM) attacks, where an attacker could intercept or modify the transmitted data. Additionally, NeuVector loads the response of the telemetry server is loaded into memory without size limitation, which makes it vulnerable to a Denial of Service(DoS) attack.
The patched version includes the following security improvements:
- NeuVector now verifies the telemetry server’s
TLS certificate chainandhostnameduring the handshake process. This ensures that all telemetry communications occur over a trusted and verified channel. - NeuVector limits the telemetry server’s response to
256 bytes, mitigating the risk of memory exhaustion and DoS attacks.
These security enhancements are enabled by default and require no user action.
The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.
CVE-2025-54470 has a CVSS score of 8.6 (High). 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-20251020133207-084a437033b4); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Patched versions include release v5.4.7 and above.
Frequently Asked Questions
- What is CVE-2025-54470? CVE-2025-54470 is a high-severity allocation of resources without limits or throttling vulnerability in github.com/neuvector/neuvector (go), affecting versions >= 0.0.0-20230727023453-1c4957d53911, < 0.0.0-20251020133207-084a437033b4. It is fixed in 0.0.0-20251020133207-084a437033b4. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
- How severe is CVE-2025-54470? CVE-2025-54470 has a CVSS score of 8.6 (High). 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.
- Which versions of github.com/neuvector/neuvector are affected by CVE-2025-54470? github.com/neuvector/neuvector (go) versions >= 0.0.0-20230727023453-1c4957d53911, < 0.0.0-20251020133207-084a437033b4 is affected.
- Is there a fix for CVE-2025-54470? Yes. CVE-2025-54470 is fixed in 0.0.0-20251020133207-084a437033b4. Upgrade to this version or later.
- Is CVE-2025-54470 exploitable, and should I be worried? Whether CVE-2025-54470 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
- What actually determines whether CVE-2025-54470 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.
- How do I fix CVE-2025-54470? Upgrade
github.com/neuvector/neuvectorto 0.0.0-20251020133207-084a437033b4 or later.