0.0
NA
CVE-2026-18749
CVE-2026-18749
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.

INFO

Published Date :

Aug. 12, 2026, 10:17 p.m.

Last Modified :

Aug. 12, 2026, 10:17 p.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-18749 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Enforce authorization checks on case attachments before granting access.
  • Verify VinceTrackAttachment.shared flag before access.
  • Update authorization logic for case artifacts.
  • Implement access control for attachment retrieval.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-18749.

URL Resource
https://github.com/CERTCC/VINCE
https://github.com/CERTCC/VINCE/pull/235
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-18749 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-18749 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-18749 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-18749 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Aug. 12, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'CERT/CC', 'product': 'VINCE', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '3.0.44', 'versionType': 'semver'}]}]
    Added 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.
    Added Reference https://github.com/CERTCC/VINCE
    Added Reference https://github.com/CERTCC/VINCE/pull/235
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.