{"id":"CVE-2025-66001","aliases":["GHSA-4jj9-cgqc-x9h5","GO-2025-4235"],"title":"NeuVector OpenID Connect is vulnerable to man-in-the-middle (MITM)","summary":"NeuVector OpenID Connect is vulnerable to man-in-the-middle (MITM)","severity":"high","cvss":8.8,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","vendor":"neuvector","product":"github.com/neuvector/neuvector","ecosystem":"go","affected":["github.com/neuvector/neuvector >= 5.3.0, < 5.4.8"],"patched":["github.com/neuvector/neuvector 5.4.8"],"published":"2025-12-12","updated":"2026-09-10","sourceUpdated":"2026-09-10T03:50:31.500340405Z","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-4jj9-cgqc-x9h5","references":[{"url":"https://github.com/neuvector/neuvector/security/advisories/GHSA-4jj9-cgqc-x9h5"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-66001"},{"url":"https://github.com/neuvector/neuvector/commit/955904b5762f296d209bf395a5fcc7a40a53c424"},{"url":"https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-66001"},{"url":"https://github.com/neuvector/neuvector"}],"tags":["osv","go"],"epss":0.00366,"epssPercentile":0.27805,"ingestedAt":"2026-09-12T03:13:01.753Z","slug":"CVE-2025-66001","body":"## Overview\n\n### Impact\n\nNeuVector 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.\nStarting from version 5.4.0, NeuVector supports TLS verification for following connection types:\n\n- Registry Connections\n- Auth Server Connections (SAML, LDAP and OIDC)\n- Webhook Connections\n\nBy default, TLS verification remains disabled, and its configuration is located under **Settings > Configuration in the NeuVector UI**.\n\nIn the patched version, the new NeuVector deployment enables TLS verification by default. \nFor rolling upgrades, NeuVector does not automatically change this setting to prevent disruptions.\n\n**Note:** When \"TLS verification\" is enabled, it affects all connections to:\n\n- Registry servers\n- Auth servers (SAML, LDAP and OIDC)\n- Webhook servers\n\n### Patches\n\nPatched versions include release v5.4.8 and above.\n\n### Workarounds\n\nTo manually enable TLS verification:\n\n1. Open the NeuVector UI.\n2. Navigate to **Settings > Configuration**.\n3. In the **TLS Self-Signed Certificate Configuration** section, select **Enable TLS verification**.\n4. (Optional) Upload or paste the **TLS self-signed certificate**.\n\n### References\n\nIf you have any questions or comments about this advisory:\n\n- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.\n- Open an issue in the [NeuVector](https://github.com/neuvector/neuvector/issues/new/choose) repository.\n- Verify with our [support matrix](https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/#suse-security).\n\n## Affected packages\n\n- `github.com/neuvector/neuvector >= 5.3.0, < 5.4.8`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `github.com/neuvector/neuvector 5.4.8`","depth":"twilight","depthScore":48,"depthScoreParts":{"impact":48.4,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}