CVE-2025-66001: NeuVector OpenID Connect is vulnerable to man-in-the-middle (MITM)
Impact 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.
Published Dec 12, 2025 · Updated Jan 8, 2026
Affected packages
github.com/neuvector/neuvector
- Ecosystem
- Go
- Affected
- >= 5.3.0, < 5.4.8
- Fixed in
- 5.4.8
- Check
go list -m github.com/neuvector/neuvector
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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
Patches
Patched versions include release v5.4.8 and above.
Workarounds
To manually enable TLS verification:
- Open the NeuVector UI.
- Navigate to Settings > Configuration.
- In the TLS Self-Signed Certificate Configuration section, select Enable TLS verification.
- (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.
References
- https://github.com/neuvector/neuvector/security/advisories/GHSA-4jj9-cgqc-x9h5
- https://github.com/neuvector/neuvector/commit/955904b5762f296d209bf395a5fcc7a40a53c424
- https://nvd.nist.gov/vuln/detail/CVE-2025-66001
- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-66001
- https://github.com/advisories/GHSA-4jj9-cgqc-x9h5
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-54469
NeuVector Enforcer is vulnerable to Command Injection and Buffer overflow
critical9.9Oct 21, 2025CVE-2025-54470
NeuVector telemetry sender is vulnerable to MITM and DoS
high8.6Oct 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
