CVE-2026-7681
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security vulnerability has been detected in jsbroks COCO Annotator up to 0.11.1. Affected by this vulnerability is an unknown functionality of the file backend/webserver/api/datasets.py of the component Dataset API. The manipulation of the argument DatasetId leads to authorization bypass. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe vulnerability exists in the Dataset API (backend/webserver/api/datasets.py) of COCO Annotator up to v0.11.1, where manipulation of the DatasetId parameter allows attackers to bypass authorization checks. This broken access control vulnerability in the web application permits unauthorized access to or manipulation of datasets via the API endpoint.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify COCO Annotator installation versionLocate the installed COCO Annotator version - check the source code version file, package.json, or application metadata. Common locations include version info in the application UI or a version file in the root directory.Affected if The installed version is v0.11.1 or any earlier version (v0.x.x where x <= 11)
-
Verify Dataset API component existsInspect the backend/webserver/api/datasets.py file in the COCO Annotator installation directory. Confirm the file exists and contains the Dataset API implementation.Affected if The file backend/webserver/api/datasets.py exists in the installation
-
Determine if web API is exposedCheck if the COCO Annotator web application is running and accessible over HTTP/HTTPS. Identify the base URL for the API endpoints.Affected if The web application API is accessible (not restricted by firewall or network controls)
-
Test DatasetId parameter authorizationSend API requests to the dataset endpoint (typically /api/datasets/) with manipulated DatasetId values. Attempt to access or modify datasets belonging to other users without proper authentication credentials.Affected if API requests with arbitrary DatasetId values succeed without proper authorization validation (requests return dataset data or allow modifications without permission checks)
A user is affected if running COCO Annotator version v0.11.1 or earlier AND the web API is accessible AND the API permits unauthorized access/modification via DatasetId parameter manipulation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authorization validation for all dataset ID parameters in the API, verifying user permissions before allowing access or modifications to datasets. Until a vendor patch is available, consider network-level restrictions to limit API exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7681 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7681 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data