https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-08T08:17:24.570029+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-265153 EUVD-2026-265153 2026-10-08T08:17:24.618056+00:00 EUVD-2026-265153 https://cve.radiocsirt.org/vuln/fkie_cve-2025-66001 fkie_cve-2025-66001 2026-10-08T08:17:24.618094+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-4jj9-cgqc-x9h5 GHSA-4jj9-cgqc-x9h5 — NeuVector OpenID Connect is vulnerable to man-in-the-middle (MITM) 2026-10-08T08:17:24.618128+00:00

Affected: Go: github.com/neuvector/neuvector

### 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:

- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/polic…