CVE-2025-66001
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNeuVector 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNeuVector supports OpenID Connect (OIDC) authentication, but TLS/SSL certificate verification for OIDC connections is not enforced by default. This allows a man-in-the-middle attacker to intercept the authentication flow, potentially capturing credentials or session tokens and impersonating the OIDC provider to gain unauthorized access to NeuVector.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify NeuVector is installedRun 'helm list' or check for neuvector pods via 'kubectl get pods -A | grep neuvector' to confirm NeuVector deployment existsAffected if NeuVector is not installed - the check does not apply
-
Check if OIDC authentication is enabledExamine NeuVector authentication configuration files or CRD: 'kubectl get authentications -n neuvector' or check /etc/neuvector/ for OIDC-related configuration filesAffected if OIDC is not enabled - the vulnerability does not apply
-
Inspect TLS certificate verification settings for OIDC providerReview OIDC configuration for 'tls_verify', 'insecure_skip_verify', 'skip_tls_verify', or similar flags. Check CRD 'kubectl get authentications <name> -n neuvector -o yaml' and look for TLS-related parameters under the OIDC provider sectionAffected if TLS certificate verification is disabled, set to false, or missing for the OIDC connection - the environment is affected
-
Compare installed NeuVector version to vendor advisoriesRun 'helm list' or 'kubectl get deployment -n neuvector' to find the installed version, then compare against CVE-2025-66001 affected version ranges if published by vendorAffected if Installed version falls within the affected range and OIDC with disabled TLS verification is in use
You are affected if OIDC authentication is enabled in NeuVector and TLS certificate verification for OIDC connections is not enforced (disabled or not configured), regardless of specific version.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataEnable and enforce TLS certificate verification for all OpenID Connect connections in NeuVector's authentication configuration to ensure proper validation of the remote OIDC provider's identity.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-66001 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data