Out-of-bounds ReadWeakness · CWE-125

CVE-2026-2810

MEDIUM · 6.8 CVSS v4.0 Published 2026-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Zero-click

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 · unedited
Netskope was notified about a potential gap in the Endpoint DLP Module for Netskope Client on Windows systems. The successful exploitation of the gap can potentially allow an unprivileged user to trigger an out-of-bounds read within a driver, leading to a Blue-Screen-of-Death (BSOD). Successful exploitation would require the Endpoint DLP module to be enabled in the client configuration. A successful exploit can potentially result in a denial-of-service for the local machine.

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 · moderate confidence

A vulnerability in the Netskope Client Endpoint DLP module for Windows allows an unprivileged local user to trigger an out-of-bounds read in a kernel-mode driver, causing a system crash (BSOD). The issue only affects systems where the Endpoint DLP module is enabled in the client configuration.

MitigationDisable the Endpoint DLP module in the Netskope Client configuration as a temporary workaround, and apply the vendor-supplied patch/update to the Netskope Client to address the driver bounds-checking issue.

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
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Netskope Client is installed
    Locate the Netskope Client executable (typically at C:\Program Files\Netskope\Netskope Client\Netskope.exe) or check for the Netskope service in Services.msc
    Affected if Netskope Client is not installed on the system, the vulnerability does not apply
  2. Identify the installed Netskope Client version
    Right-click Netskope.exe, select Properties, and note the File Version, or run 'wmic product get name,version' filtering for Netskope
    Affected if The installed version falls within the vulnerable version range for CVE-2026-2810; compare your version to the affected releases from Netskope's security advisory
  3. Verify if Endpoint DLP module is enabled
    Open the Netskope Client UI, navigate to Settings or Policy configuration, and locate the Endpoint DLP module status; alternatively, check the Netskope configuration file (often netskope.conf or registry key under HKLM\SOFTWARE\Netskope\NetskopeClient) for a DLP-enabled flag
    Affected if The Endpoint DLP module is enabled in the Netskope Client configuration - this is the required condition for the vulnerability to be exploitable
  4. Confirm kernel driver presence
    Check for Netskope kernel-mode driver files in C:\Windows\System32\drivers (typically nskdlp.sys or similar DLP-related driver), or list drivers via 'driverquery /v' looking for Netskope-related entries
    Affected if The Netskope DLP kernel driver is loaded on the system, which is required for the out-of-bounds read to occur

A user is affected if Netskope Client is installed with a vulnerable version, AND the Endpoint DLP module is enabled, AND the corresponding kernel driver is loaded, allowing an unprivileged local user to trigger the BSOD condition.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the Endpoint DLP module in the Netskope Client configuration as a temporary workaround, and apply the vendor-supplied patch/update to the Netskope Client to address the driver bounds-checking issue.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2810 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2810 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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