# CVE-2025-23294: Command injection in NVIDIA WebDataset

> Attackers can execute arbitrary code with elevated permissions in NVIDIA WebDataset, leading to privilege escalation, data tampering, and denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 13 Aug 2025
- **Updated:** 13 Aug 2025
- **Also known as:** GHSA-7j3c-mf9v-qv7q

## What is CVE-2025-23294?

CVE-2025-23294 is a high-severity command injection vulnerability in NVIDIA WebDataset, published on 13 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA WebDataset for all platforms contains a vulnerability where an attacker could execute arbitrary code with elevated permissions. A successful exploit of this vulnerability might lead to escalation of privileges, data tampering, information disclosure, and denial of service.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-23294 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23294 is a high-severity command injection vulnerability in NVIDIA WebDataset, published on 13 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-23294 in the wild and no public exploit code.

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

## Sources

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

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