# CVE-2026-18749: CVE-2026-18749

> Attackers can access unshared coordinator artifacts by guessing UUIDs, leaking sensitive data to unauthorized case members.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-fmgm-gh7c-hwv2

## What is CVE-2026-18749?

CVE-2026-18749 is a critical missing authorization vulnerability in CERT/CC VINCE, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The type=track branch authorises on _is_my_case(t_attach.case) only and never checks VinceTrackAttachment.shared. A coordinator-uploaded case artefact that has NOT been marked shared is still retrievable by any case member who has (or is sent) its uuid — leaks not-yet-released coordinator material to vendors on the case.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-18749 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18749 is a critical missing authorization vulnerability in CERT/CC VINCE, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18749 in the wild and no public exploit code.

Affected product: CERT/CC VINCE. 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-18749/ (Markdown: https://insights.sbomify.com/CVE-2026-18749/index.md)
```

## Sources

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

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