CVE-2025-54470: NeuVector telemetry sender is vulnerable to MITM and DoS
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.
Published Oct 21, 2025 · Updated Jul 2, 2026
Affected packages
github.com/neuvector/neuvector
- Ecosystem
- Go
- Affected
- >= 0.0.0-20230727023453-1c4957d53911, < 0.0.0-20251020133207-084a437033b4
- Fixed in
- 0.0.0-20251020133207-084a437033b4
- Check
go list -m github.com/neuvector/neuvector
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Patches
Patched versions include release v5.4.7 and above.
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.
Credited to mmalesev, holyspectral.
References
- https://github.com/neuvector/neuvector/security/advisories/GHSA-qqj3-g7mx-5p4w
- https://github.com/neuvector/neuvector/commit/06424701e69bf1eb76ff90180d78853fded93021
- https://github.com/neuvector/neuvector/commit/415737cbec581a5dc5f204fac1c78b7f29ad7dc2
- https://nvd.nist.gov/vuln/detail/CVE-2025-54470
- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-54470
- https://github.com/advisories/GHSA-qqj3-g7mx-5p4w
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-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-54467
NeuVector process with sensitive arguments lead to leakage
medium5.3Aug 28, 2025CVE-2025-8077
NeuVector admin account has insecure default password
critical9.8Aug 28, 2025
