CVE-2025-66001: Github.com/neuvector/neuvector NeuVector OpenID Connect Is Vulnerable Vulnerability

HIGH
Advisory Identifier: GHSA-4jj9-cgqc-x9h5
CVSS 8.8
CWE-295
Published
Advisory Summary

CVE-2025-66001 is a HIGH (CVSS 8.8) neuvector openid connect is vulnerable vulnerability (CWE-295: Improper Certificate Validation) affecting Github.com/neuvector/neuvector libraries in the Go ecosystem. The issue involves neuvector openid connect is vulnerable to man-in-the-middle (mitm). Remediation is available by upgrading affected packages to version 5.4.8.

CVE-2025-66001 at a Glance

CVE Identifier CVE-2025-66001
GHSA Identifier GHSA-4jj9-cgqc-x9h5
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-295: Improper Certificate Validation
Affected Product Github.com/neuvector/neuvector
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2025-66001

To remediate this vulnerability, upgrade all affected Github.com/neuvector/neuvector dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/neuvector/neuvector fixed: 5.4.8
Upgrade github.com/neuvector/neuvector to 5.4.8
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/neuvector/neuvector

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-66001, inspect your project dependencies for Github.com/neuvector/neuvector:

inspect dependencies for github.com/neuvector/neuvector

Analyze the terminal output to locate any version of Github.com/neuvector/neuvector in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.4.8), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-295: Improper Certificate Validation, where the product does not validate, or incorrectly validates, a certificate. In Github.com/neuvector/neuvector, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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/policy) for security related inquiries. - Open an issue in the [NeuVector](https://github.com/neuvector/neuvector/issues/new/choose) repository. - 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).

CVE-2025-66001 Affected Github.com/neuvector/neuvector Versions

1 component(s)
Fixed Versions:
5.4.8
Product / Package Ecosystem Affected Versions Fixed Version
github.com/neuvector/neuvector
Go
≥ 5.3.0
< 5.4.8
5.4.8

References

Frequently Asked Questions

What is CVE-2025-66001?
CVE-2025-66001 is a security vulnerability in Github.com/neuvector/neuvector involving NeuVector OpenID Connect is vulnerable to man-in-the-middle (MITM) under CWE-295: Improper Certificate Validation.
Which Github.com/neuvector/neuvector versions are affected?
Affected versions include releases prior to 5.4.8 across affected packages: github.com/neuvector/neuvector.
What version fixes CVE-2025-66001?
Upgrading to 5.4.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/neuvector/neuvector affected?
Yes, github.com/neuvector/neuvector is affected in releases prior to 5.4.8. Upgrade your dependency to 5.4.8 or later.
What is the CVSS score of CVE-2025-66001?
CVE-2025-66001 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2025-66001?
CVE-2025-66001 is classified under CWE-295: Improper Certificate Validation (The product does not validate, or incorrectly validates, a certificate.).
How can I check Go dependencies for CVE-2025-66001?
Run the dependency tree command: 'inspect dependencies for github.com/neuvector/neuvector'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4jj9-cgqc-x9h5",
  "modified" : "2026-01-08T20:51:32Z",
  "published" : "2025-12-12T19:22:04Z",
  "aliases" : [ "CVE-2025-66001" ],
  "summary" : "NeuVector OpenID Connect is vulnerable to man-in-the-middle (MITM)",
  "details" : "### 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).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/neuvector/neuvector"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.3.0"
      }, {
        "fixed" : "5.4.8"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/neuvector/neuvector/security/advisories/GHSA-4jj9-cgqc-x9h5"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-66001"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/neuvector/neuvector/commit/955904b5762f296d209bf395a5fcc7a40a53c424"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-66001"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/neuvector/neuvector"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-295" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-12T19:22:04Z",
    "nvd_published_at" : "2026-01-08T11:15:43Z"
  }
}