# CVE-2025-23252: Information disclosure in NVDebug tool

> An attacker can gain access to restricted components in the NVIDIA NVDebug tool, leading to information disclosure.

- **Severity:** Medium 4.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jun 2025
- **Updated:** 18 Jun 2025
- **Also known as:** GHSA-gc52-j4fw-h449

## What is CVE-2025-23252?

CVE-2025-23252 is a medium-severity vulnerability in NVIDIA NVDebug tool, published on 18 Jun 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The NVIDIA NVDebug tool contains a vulnerability that may allow an actor to gain access to restricted components. A successful exploit of this vulnerability may lead to information disclosure.

Weakness: CWE-1244 (Internal Asset Exposed to Unsafe Debug Access Level or State)

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

It affects 1 product.


Products: Nvidia Nvdebug.

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

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

## Is CVE-2025-23252 being exploited?

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

## Other vulnerabilities in NVIDIA NVDebug tool

- [CVE-2025-23342](https://insights.sbomify.com/CVE-2025-23342/): Privilege escalation in NVDebug tool (high 8.2)
- [CVE-2025-23343](https://insights.sbomify.com/CVE-2025-23343/): Path traversal in NVDebug tool (high 7.6)
- [CVE-2025-23344](https://insights.sbomify.com/CVE-2025-23344/): Command injection in NVDebug tool (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23252 is a medium-severity vulnerability in NVIDIA NVDebug tool, published on 18 Jun 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-23252 in the wild and no public exploit code.

Affected product: NVIDIA NVDebug tool. 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-23252/ (Markdown: https://insights.sbomify.com/CVE-2025-23252/index.md)
```

## Sources

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

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