Skip to main content
CVE-2025-11156VulnerabilityPublished

CVE-2025-11156: Netskope Client · NULL Pointer Dereference

Affects Netskope ClientSource CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Netskope Netskope ClientAffected
  • =0
Fixed in–

AI-suggested

To mitigate CVE-2025-11156, organizations should implement the following specific measures: 1) Restrict administrative privileges strictly to trusted personnel and enforce least privilege principles to reduce the risk of exploitation. 2) Monitor and audit the use of administrative accounts on endpoints running Netskope Client to detect suspicious activity or unauthorized driver loading attempts. 3) Apply any available patches or updates from Netskope as soon as they are released, as no patches are currently available. 4) Implement endpoint protection solutions that can detect and block abnormal kernel driver loading behaviors. 5) Use application whitelisting or driver signing enforcement policies to prevent unauthorized or improper driver loads. 6) Educate administrators about the risks of improper driver loading and ensure secure configuration of the Netskope Client. 7) Maintain robust incident response plans to quickly recover from potential DoS conditions caused by this vulnerability. 8) Consider network segmentation and isolation of critical systems to limit the impact of potential insider attacks exploiting this flaw.

Description

Netskope was notified about a potential gap in its agent (NS Client) on Windows systems. If this gap is successfully exploited, a local, authenticated user with Administrator privileges can improperly load the driver as a generic kernel service. This triggers the flaw, causing a system crash (Blue-Screen-of-Death) and resulting in a Denial of Service (DoS) for the affected machine.

References

Community reviews

Loading reviews…