CVE-2026-7680: jsbroks COCO Annotator Data Endpoint datasets.py path traversal
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.
Security readout for executives and security teams
Plain-English summary
COCO Annotator 0.11.0 and 0.11.1 contain a remotely reachable path-traversal weakness in a dataset endpoint. A low-privileged user may manipulate the dataset folder value to reach paths outside the intended location, creating a limited confidentiality risk. Public exploit material exists, but the supplied sources do not establish active exploitation.
Executive priority
Treat this as a moderate-priority confidentiality issue. Accelerate action for internet-accessible deployments, environments holding sensitive files, or broadly assigned user access. Restrict exposure immediately where practical, then track vendor or project guidance. Current evidence does not justify describing this as an actively exploited emergency.
Technical view
The weakness affects an unspecified function in backend/webserver/api/datasets.py within the Data Endpoint. Manipulating the folder argument can trigger CWE-22 path traversal. CVSS 4.0 rates it 5.3, with network access, low complexity, low privileges, no user interaction, and low confidentiality impact. No integrity or availability impact is identified.
Likely exposure
Exposure is most likely where COCO Annotator 0.11.0 or 0.11.1 is deployed and its Data Endpoint is accessible to untrusted or low-privileged users. Internet-accessible instances warrant faster review. The supplied evidence does not identify other affected versions, default exposure, authentication configuration, or the specific files obtainable.
Exploitation context
A public exploit reference is available, increasing the chance of attempted abuse. The CVSS vector indicates low privileges are required, so this is not documented as unauthenticated exploitation. CVE-2026-7680 is not listed as KEV in the supplied bundle, and no cited evidence confirms exploitation in the wild.
Researcher notes
The available description does not identify the exact function, vulnerable code path, accessible file scope, default authentication posture, or a fixed version. Vendor contact reportedly received no response. Assessment therefore relies on CWE-22, the CVSS vector, affected-version data, and the public research reference; avoid assuming arbitrary file access beyond demonstrated scope.
Mitigation direction
Inventory COCO Annotator deployments and prioritize versions 0.11.0 and 0.11.1.
Restrict the Data Endpoint to trusted networks and authorized users until remediation is available.
Apply least-privilege filesystem permissions to limit data accessible through the application.
Check current vendor or project guidance for a fixed release; no patch is identified in supplied sources.
Consider application-layer validation that confines folder values to approved dataset directories.
Validation and detection
Confirm deployed COCO Annotator versions from package, image, or build records.
Determine whether the Data Endpoint is reachable from untrusted networks or low-privileged accounts.
Review endpoint logs for anomalous folder values or access outside expected dataset locations.
Verify filesystem permissions prevent the service account from reading unnecessary sensitive files.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.