# CVE-2026-7680: jsbroks COCO Annotator Data Endpoint datasets.py path traversal

> Remote attackers can exploit a path traversal vulnerability in the COCO Annotator data endpoint to access unauthorized files.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 3 May 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-q3jg-8pmp-625w

## What is CVE-2026-7680?

CVE-2026-7680 is a medium-severity path traversal vulnerability in jsbroks COCO Annotator, published on 3 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in jsbroks COCO Annotator up to 0.11.1. Affected is an unknown function of the file backend/webserver/api/datasets.py of the component Data Endpoint. Executing a manipulation of the argument folder can lead to path traversal. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2026-7680 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7680 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7680 is a medium-severity path traversal vulnerability in jsbroks COCO Annotator, published on 3 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7680 exists.

Affected product: jsbroks COCO Annotator. 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-7680/ (Markdown: https://insights.sbomify.com/CVE-2026-7680/index.md)
```

## Sources

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

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