# CVE-2025-5941: Out-of-Bounds Read Vulnerability in Netskope Client

> A malicious actor can trigger a memory leak via crafted DNS packets, potentially exposing user-controllable memory in domain names stored locally.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2025
- **Updated:** 15 Aug 2025
- **Also known as:** GHSA-7cpx-2f4q-g73f

## What is CVE-2025-5941?

CVE-2025-5941 is a low-severity vulnerability in Netskope Client, published on 14 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Netskope is notified about a potential gap in its agent (NS Client) in which a malicious actor could trigger a memory leak by sending a crafted DNS packet to a machine. A successful exploitation may require administrative privileges on the machine, based on the exact configuration. A successful exploit can potentially result in user-controllable memory being leaked in a domain name stored on the local machine.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-5941?


## How do I fix CVE-2025-5941?

No fix has been published for CVE-2025-5941 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5941 being exploited?

There is no known exploitation of CVE-2025-5941 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5941 and fix it if it is affected.

What it is: CVE-2025-5941 is a low-severity vulnerability in Netskope Client, published on 14 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5941 in the wild and no public exploit code.

Affected product: Netskope Client. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5941/ (Markdown: https://insights.sbomify.com/CVE-2025-5941/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5941
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5941
- OSV: https://osv.dev/vulnerability/CVE-2025-5941

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5941/
Summaries are generated and may contain mistakes; the official description above is the record.