CVE-2026-18749: CERT/CC VINCE · Insecure Direct Object Reference
Affects CERT/CC VINCESource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.0.44 as a priority.
Data as of 11 Nov 2026, 23:24 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.0.44
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade CERT/CC VINCE to 3.0.44.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CERT/CCVINCE | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict distribution of artefact UUIDs to trusted parties only and review access control policies to ensure that artefact sharing flags are properly enforced.
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.