Anti-tampering bypass via exposed driver IOCTL
Published Jun 17, 2026 · Updated Jun 17, 2026
Insufficient IOCTL access control in Netskope Client before R138 allows local administrators to bypass NSClient anti-tampering protections. The Windows driver accepts crafted requests to a customer IOCTL without sufficient access control, allowing its anti-tampering state to be altered. Administrative privileges on a Windows endpoint are required; the demonstrated consequence is disabling NSClient protections, not broader code execution.
Summary
What happened
Insufficient IOCTL access control in Netskope Client before R138 allows local administrators to bypass NSClient anti-tampering protections. The Windows driver accepts crafted requests to a customer IOCTL without sufficient access control, allowing its anti-tampering state to be altered. Administrative privileges on a Windows endpoint are required; the demonstrated consequence is disabling NSClient protections, not broader code execution.
The record
- CVE
- CVE-2025-15641
- Published
- Jun 17, 2026
- Updated
- Jun 17, 2026
- Vendor
- Netskope
- Product
- Netskope Client
- Classifications
- CWE-782, CAPEC-176, T1562.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 17, 2026CVE publishedPublication date reported by the CVE source.
- Jun 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <138
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo