Security Advisories and CVEs
NeuVector is committed to informing the community about security issues. The following table lists published security advisories and CVEs (Common Vulnerabilities and Exposures) for resolved issues.
CVE List​
| ID | Description | Date | Resolution |
|---|---|---|---|
| CVE-2025-66001 | In the patched version, new NeuVector deployments enable TLS verification by default. For rolling upgrades, NeuVector does not change this setting automatically to avoid disruption. | 12 Dec 2025 | NeuVector v5.4.8 |
| CVE-2025-54471 | NeuVector uses dynamically generated encryption keys and securely stores them in Kubernetes secrets. This improvement replaces previously hardcoded cryptographic material, enhancing data confidentiality and operational security in all deployments. | 17 Oct 2025 | NeuVector v5.4.7 |
| CVE-2025-54470 | NeuVector enforces TLS certificate and hostname verification for all telemetry communications. In addition, it limits telemetry response size to prevent denial-of-service risks. These enhancements ensure telemetry data is exchanged securely and efficiently. | 17 Oct 2025 | NeuVector v5.4.7 |
| CVE-2025-54469 | NeuVector strengthened the enforcer’s monitor process by validating environment variables before execution. This change prevents unsafe command execution and improves overall runtime security and process integrity. | 17 Oct 2025 | NeuVector v5.4.7 |
| CVE-2025-8077 | For NeuVector deployments on Kubernetes-based environments, the bootstrap password of the default admin user is now generated randomly and stored in a Kubernetes secret. The default admin must retrieve the bootstrap password from the secret and change it after the first successful UI login. | 25 Aug 2025 | NeuVector v5.4.6 |
| CVE-2025-53884 | NeuVector now uses a cryptographically secure salt with the PBKDF2 algorithm instead of a simple hash to protect user passwords. During rolling upgrades from earlier versions, NeuVector recalculates and stores the new password hash after each user’s next successful login. | 25 Aug 2025 | NeuVector v5.4.6 |
| CVE-2025-54467 | NeuVector now redacts process commands containing password, passwd, pwd, token, or key from logs and debug outputs by default. Users can configure a Kubernetes ConfigMap to define additional regex patterns for redaction. | 25 Aug 2025 | NeuVector v5.4.6 |
| CVE-2025-46808 | Sensitive information may be logged in the manager container depending on logging configuration and credential permissions. | 09 Jul 2025 | NeuVector v5.4.5 |
| CVE-2024-38095 | In .NET, a malicious X.509 certificate or chain can cause excessive CPU use, leading to denial of service. This CVE was flagged as an affected .NET library detection issue. | 9 Jul 2025 | NeuVector v5.4.5 |
| CVE-2024-7347 | The NGINX ngx_http_mp4_module vulnerability allows crafted MP4 files to cause memory over-reads and worker process termination. Reported in NeuVector 5.4.2 as a possible false negative detection in the vulnerability scanner; not a NeuVector product issue. | 15 Jan 2025 | NeuVector v5.4.2 |
| CVE-2018-20796 | In the GNU C Library through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has uncontrolled recursion. | 15 Jan 2025 | Not applicable, flagged in v5.4.2 as a false positive. |
| CVE-2024-41110 | A security vulnerability in some Docker Engine versions may allow an attacker to bypass authorization plugins (AuthZ). The likelihood of exploitation is low. | 16 Nov 2024 | NeuVector v5.4.1 |
| CVE-2020-26160 | jwt-go allows attackers to bypass access restrictions when []string{} is used for m["aud"]. Users should migrate to golang-jwt v3.2.1. | 16 Nov 2024 | NeuVector v5.4.1 |
Questions and Support​
- Contact the SUSE Rancher Security team.
- Open an issue in the NeuVector GitHub repository.
- References: