Skip to content

NeuVector OpenID Connect is vulnerable to man-in-the-middle (MITM)

High severity GitHub Reviewed Published Dec 12, 2025 in neuvector/neuvector • Updated Dec 12, 2025

Package

gomod github.com/neuvector/neuvector (Go)

Affected versions

>= 5.3.0, < 5.4.8

Patched versions

5.4.8

Description

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

@samjustus samjustus published to neuvector/neuvector Dec 12, 2025
Published to the GitHub Advisory Database Dec 12, 2025
Reviewed Dec 12, 2025
Last updated Dec 12, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

Weaknesses

Improper Certificate Validation

The product does not validate, or incorrectly validates, a certificate. Learn more on MITRE.

CVE ID

CVE-2025-66001

GHSA ID

GHSA-4jj9-cgqc-x9h5

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.