/

CVE-2026-18749

Severity:

CRITICAL RISK

(9.8)

Broken Access Control (CWE-639) in VinceTrack Attachments

CVE-2026-18749

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-639

Impact:

Unauthorized disclosure of sensitive case artefacts

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A broken access control vulnerability in VinceTrack attachment retrieval allows case members to access coordinator-uploaded artefacts that have not been marked as shared. An attacker who knows or receives an attachment UUID may retrieve unreleased case material because authorization checks case membership but do not verify the attachment's sharing state.

Affected context

The issue occurs in the type=track attachment retrieval path when VinceTrack authorizes access based on _is_my_case(t_attach.case) without also checking VinceTrackAttachment.shared. Deployments are exposed when coordinator-uploaded files remain private or unreleased while other members, including vendors associated with the case, can submit or obtain their UUIDs.

Exploit preconditions

  • Attack surface: Authenticated attachment retrieval through the type=track application path
  • Required access: Membership in the relevant case, along with possession or receipt of the attachment UUID
  • Trigger point: A request to retrieve a track attachment by UUID
  • Why exploitation is possible: The authorization decision verifies case membership but omits the attachment's shared status, allowing access to artefacts that are not intended for release

Why this happens

The underlying flaw is an incomplete object-level authorization check. The application treats membership in the parent case as sufficient authorization for a child attachment, without enforcing the attachment's own confidentiality or release state.

This maps to CWE-639: Authorization Bypass Through User-Controlled Key, because a user-controlled or user-supplied identifier can select an object whose access decision does not fully account for its ownership and sharing attributes.

Potential impact

  • Unauthorized users may retrieve unreleased coordinator material
  • Confidential case documents may be disclosed to vendors or other case members
  • Legal, commercial, or operational information could be exposed
  • The organization may face privacy, compliance, or contractual consequences

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the attachment-object level rather than relying solely on parent-case membership.

Common defensive patterns include:

  • Require both valid case authorization and an explicit shared or released state before serving an attachment
  • Apply deny-by-default access decisions for private artefacts
  • Bind attachment retrieval to the authenticated principal and permitted case role
  • Avoid treating possession of an attachment UUID as evidence of authorization
  • Centralize object-level authorization checks so all retrieval paths use the same policy
  • Use least-privilege roles and separate coordinator, vendor, and case-member permissions
  • Log and review access to unreleased attachments

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis and code review checks for authorization decisions based only on parent-object membership
  • Review of handlers that retrieve records directly from user-supplied identifiers
  • Tests covering private, shared, released, and cross-role attachment states
  • Policy checks requiring object-level authorization before file or record retrieval
  • Runtime monitoring for access to unreleased artefacts by users without explicit release permissions
  • Automated security review tools that flag missing ownership, visibility, or state checks

Sources

SourceLink
github.comgithub.com/CERTCC/VINCE
github.comgithub.com/CERTCC/VINCE/pull/235

Frequently asked

questions

Yes, within the application's authenticated attack surface. An attacker does not need server access if they can use the attachment retrieval endpoint as a case member and obtain a valid attachment UUID.

The described flaw requires membership in the relevant case and knowledge or receipt of the target attachment identifier. The attacker may not need coordinator privileges.

Enforce object-level authorization that checks case membership, the attachment's sharing or release state, and the user's role before returning any attachment content.

Use deny-by-default policies, centralize authorization logic, test every visibility state and role combination, and monitor access to private or unreleased objects.

Find out what's already
exploitable in your codebase.