Skip to main content
Menu
CVEs

CVE

Netskope Client local privilege escalation via OpenSSL config loading

Affects Netskope Client and Endpoint DLP on endpoints with a secondary drive. Fixed in R142.0.0 or later, or in maintenance updates R141 (141.1.13.2833), R138 (138.1.16.2834), and R135 (135.1.27.2835).

CVE-2026-15707EUVD-2026-126290GHSA-H8QH-2PM3-W8MM

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/S:N

8.5HighCNA
Exploited
No known exploitation
Fix
Fixed in R142.0.0 or later, R141 (141.1.13.2833 and above), R138 (138.1.16.2834 and above), R135 (135.1.27.2835 and above)
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Endpoint has a secondary drive

Published
Last modified
Reference
Last checked
15/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

Netskope Client and Netskope Endpoint DLP on Windows let a local attacker with low-level access run code with SYSTEM privileges. The attacker places a malicious OpenSSL configuration file in a root-level folder on a secondary drive, where standard users can create directories by default, and the services load it when they start or the system reboots.

Original description

An uncontrolled search path vulnerability (CWE-427) in statically linked OpenSSL libraries within Netskope Client (stAgentSvc.exe) and Endpoint DLP (epdlp.exe) on Windows allows an authenticated local attacker to execute arbitrary code with elevated SYSTEM privileges. The services retain internal build-time paths referencing a secondary drive location. On Windows systems where default volume permissions allow standard users to create root-level directories on secondary drives, an attacker can place a malicious configuration file (openssl.cnf) that is loaded under the NT AUTHORITY\SYSTEM context upon service startup or system reboot. Under default operating system permissions, macOS and Linux are not susceptible, and mobile platforms are unaffected.

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.5/10CVSS 8.5, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Endpoint has a secondary drive
  • Upgrade to a fixed version: R142.0.0 or later, R141 (141.1.13.2833 and above), R138 (138.1.16.2834 and above), R135 (135.1.27.2835 and above).

  • Workaround: Restrict folder and file creation permissions for unprivileged users on the root of secondary volumes using Windows Access Control Lists (icacls).

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-15707 (Netskope Client and Endpoint DLP Local Privilege Escalation via Insecure OpenSSL Configuration), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-15707 (entry last updated 2026-11-16):
Affected:
- Netskope Netskope Client: version range not reported
- Netskope Netskope Endpoint DLP: version range not reported
Fixed versions: R142.0.0 or later, R141 (141.1.13.2833 and above), R138 (138.1.16.2834 and above), R135 (135.1.27.2835 and above).
Conditions (all must be true for the bug to be hit):
- Endpoint has a secondary drive (source: https://www.cve.org/CVERecord?id=CVE-2026-15707)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
Workaround: Restrict folder and file creation permissions for unprivileged users on the root of secondary volumes using Windows Access Control Lists (icacls). (source: https://www.cve.org/CVERecord?id=CVE-2026-15707)
CISA KEV: CVE-2026-15707 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-15707 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.netskope.com/resources/netskope-resources/netskope-security-advisory-nskpsa-2026-005
- https://www.cve.org/CVERecord?id=CVE-2026-15707
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-15707
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-15707"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • Netskope Netskope Client

    Version range not reported

  • Netskope Netskope Endpoint DLP

    Version range not reported

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-15707

Is CVE-2026-15707 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

This is a local privilege escalation in Netskope Client and Endpoint DLP, tied to an insecure OpenSSL configuration. The vendor's workaround concerns folder and file creation permissions on the root of secondary volumes, which indicates where the weakness sits.Source: cve.org

Am I affected, and how do I check?

Netskope Client and Netskope Endpoint DLP are named, and the vendor says endpoints without secondary drives are not susceptible. To check, look for a secondary drive on the endpoint and compare the installed client version with the fixed builds listed in the advisory.Source: cve.org

How do I fix CVE-2026-15707?

Upgrade to Netskope Client and Endpoint DLP R142.0.0 or later, or apply the maintenance update for the release line in use: R141 141.1.13.2833 or above, R138 138.1.16.2834 or above, or R135 135.1.27.2835 or above.Source: cve.org