CVE-2026-18749

CVE-2026-18749

Published Aug 12, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability in VINCE’s type=track branch allows a user to retrieve attachments that have not been marked as shared. By omitting the shared flag check, any case member who knows an attachment’s UUID can access it. This bypass undermines the confidentiality controls intended for coordinator‑uploaded material, potentially exposing not‑yet‑released information to all members on the case. This is an improper access control flaw and privilege escalation via permission chains (CWE‑639).

Affected Systems

Affected systems are any installations of the VINCE project, as modified by CERT/CC:VINCE. Version information is not specified in the advisory, so all releases using the current type=track implementation are potentially vulnerable. The flaw resides in the authorisation logic, not in the underlying storage, meaning any deployment that incorporates the unpatched code is at risk.

Risk and Exploitability

The exploitability is high because the required input—the UUID of an attachment—is typically known or can be intercepted between members. The vulnerability is a pure authorisation flaw; no remote code execution or elevated privilege is required. The CVSS score of 9.8 indicates critical severity, and the EPSS score of less than 1% suggests a low probability of exploitation in the wild, yet the risk of confidential data exposure remains significant for any organization using VINCE with shared‑tracking unprotected.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the patch from the pull request at https://github.com/CERTCC/VINCE/pull/235 or update to a later version of VINCE that includes the fix.
  • Audit all attachments that were uploaded before the patch and set the shared flag appropriately, removing any that should not have been exposed.
  • Reinforce access controls by adding an explicit check for the shared flag in the attachment retrieval workflow and disallowing UUID‑based access to non‑shared items.

Generated by OpenCVE AI on August 13, 2026 at 19:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-284
CWE-285
Type Values Removed Values Added
Weaknesses CWE-639
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Cert
Cert vince
Vendors & Products Cert
Cert vince
Type Values Removed Values Added
Weaknesses CWE-284
CWE-285
Type Values Removed Values 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.
Title CVE-2026-18749
References
Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
certcc
Published
Updated
Aug 13, 2026, 3:46 PM
Reserved
Aug 3, 2026, 9:27 PM
Status
Deferred
Published
Aug 12, 2026, 10:17 PM
Modified
Oct 23, 2026, 7:10 PM