# CVE-2026-47682: CVAT: Missing path-containment validation in multiple entry points allows arbitrary path writes

> Attackers with cloud storage access can overwrite arbitrary server files due to missing path validation in CVAT.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-6f87-4g86-p9gw

## What is CVE-2026-47682?

CVE-2026-47682 is a high-severity path traversal vulnerability in cvat-ai cvat, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CVAT is an open source interactive video and image annotation tool for computer vision. In versions 1.6.0 through 2.64.0, an attacker with write access to a cloud storage that's been added to a CVAT instance, or ability to add new cloud storages, is able to overwrite arbitrary files on the server's filesystem. This issue has been fixed in version 2.65.0.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-47682?


## How do I fix CVE-2026-47682?

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

## Is CVE-2026-47682 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47682 and fix it if it is affected.

What it is: CVE-2026-47682 is a high-severity path traversal vulnerability in cvat-ai cvat, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47682 in the wild and no public exploit code.

Affected product: cvat-ai cvat. 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-2026-47682/ (Markdown: https://insights.sbomify.com/CVE-2026-47682/index.md)
```

## Sources

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

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