# CVE-2025-33208: Path traversal in TAO

> An attacker can exploit an uncontrolled search path in NVIDIA TAO to escalate privileges, tamper with data, cause denial of service, or disclose information.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Dec 2025
- **Updated:** 3 Dec 2025
- **Also known as:** GHSA-p2mv-5r7j-x4hh

## What is CVE-2025-33208?

CVE-2025-33208 is a high-severity path traversal vulnerability in NVIDIA TAO, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

NVIDIA TAO contains a vulnerability where an attacker may cause a resource to be loaded via an uncontrolled search path. A successful exploit of this vulnerability may lead to escalation of privileges, data tampering, denial of service, information disclosure.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Nvidia Tao Toolkit.

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

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

## Is CVE-2025-33208 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-33208 is a high-severity path traversal vulnerability in NVIDIA TAO, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-33208 in the wild and no public exploit code.

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

## Sources

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

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