CVE-2025-66001: GO-2025-4235 - NeuVector OpenID Connect is vulnerable to man-in-the-middle (MITM) in github.com/neuvector/neuvector

CVE-2025-66001 · Severity: high · CVSS 8.8 · Published 2026-01-08

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.

Technologies: github.com/neuvector/neuvector (Go). Vendors: Go.

Quick answers

Is CVE-2025-66001 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-66001 being exploited in the wild.
How severe is CVE-2025-66001?
High severity, with a CVSS score of 8.8, published 8 January 2026.
Which products and versions are affected?
github.com/neuvector/neuvector (Go) SEMVER:introduced=0, SEMVER:introduced=5.3.0,fixed=5.4.8.
Is there a fix for CVE-2025-66001?
Yes. github.com/neuvector/neuvector (Go): upgrade to 5.4.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-66001?
Check whether you run github.com/neuvector/neuvector (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/neuvector/neuvector (Go): upgrade to 5.4.8 or later
    go get github.com/neuvector/neuvector@v5.4.8

Affected products

  • github.com/neuvector/neuvector (Go) SEMVER:introduced=0, SEMVER:introduced=5.3.0,fixed=5.4.8

Identifiers

  • CVE-2025-66001
  • GHSA-4jj9-cgqc-x9h5
  • GO-2025-4235

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.