CVE-2025-66001

Workarounds

To manually enable TLS verification:

1. Open the NeuVector UI.
2. Navigate to Settings > Configuration.
3. In the TLS Self-Signed Certificate Configuration section, select Enable TLS verification.
4. (Optional) Upload or paste the TLS self-signed certificate.

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 supports login authentication through OpenID Connect. However, the TLS verification (which verifies the remote server's authenticity and integrity) for OpenID Connect is not enforced by default. As a result this may expose the system to man-in-the-middle (MITM) attacks.
Starting from version 5.4.0, NeuVector supports TLS verification for following connection types:

• Registry Connections
• Auth Server Connections (SAML, LDAP and OIDC)
• Webhook Connections

By default, TLS verification remains disabled, and its configuration is located under Settings > Configuration in the NeuVector UI.

In the patched version, the new NeuVector deployment enables TLS verification by default.
For rolling upgrades, NeuVector does not automatically change this setting to prevent disruptions.

Note: When "TLS verification" is enabled, it affects all connections to:

• Registry servers
• Auth servers (SAML, LDAP and OIDC)
• Webhook servers

CVE-2025-66001 has a CVSS score of 8.8 (High). The vector is network-reachable, no privileges required, and user interaction required. 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 (5.4.8); upgrading removes the vulnerable code path.

Kodem intelligence

Patched versions include release v5.4.8 and above.

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