CVE-2026-15707: Netskope Client and Endpoint DLP Local Privilege Escalation via Insecure OpenSSL Configuration

Published Nov 16, 2026
·
Updated

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.

Affected Software

2 affected components
Netskope Netskope Client
Netskope Endpoint DLP

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Netskope Client and Endpoint DLP to a version that resolves this vulnerability.

    Fixed in R142.0.0
  2. Upgrade

    Upgrade Netskope Client and Endpoint DLP to a version that resolves this vulnerability.

    Fixed in 141.1.13.2833
  3. Upgrade

    Upgrade Netskope Client and Endpoint DLP to a version that resolves this vulnerability.

    Fixed in 138.1.16.2834
  4. Upgrade

    Upgrade Netskope Client and Endpoint DLP to a version that resolves this vulnerability.

    Fixed in 135.1.27.2835

Event History

Nov 16, 2026
CVE Published
via MITRE·11:54 AM
Data Sourced
via MITRE·11:54 AM
RemedyDescriptionWeakness

Frequently Asked Questions

1

Which systems are exposed to this issue?

Windows systems running the affected Netskope Client or Endpoint DLP services may be exposed when a secondary drive permits standard users to create directories at its root. macOS and Linux are not susceptible under default operating system permissions, and mobile platforms are unaffected.

2

What does an attacker need to exploit it?

An attacker needs authenticated local access to the Windows system and the ability to create the relevant root-level directory on a secondary drive. They can place a malicious openssl.cnf file there, which is loaded as SYSTEM when the affected service starts or the system reboots.

3

When would exploitation take effect?

The malicious configuration is loaded upon affected service startup or during a system reboot. Successful exploitation results in arbitrary code execution with NT AUTHORITY\SYSTEM privileges.

4

What can be done if patching cannot be performed immediately?

Restrict standard users from creating root-level directories on secondary drives, since this condition enables placement of the malicious configuration file. Review secondary-drive volume permissions on Windows hosts running the affected services.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203