NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2025-66001: NeuVector OpenID Connect is vulnerable to man-in-the-middle (MITM)

highCVSS 3.1 8.8GHSA-4jj9-cgqc-x9h5

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:

  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:

References

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 entries