Skip to main content
CVE-2025-8000VulnerabilityPublished

CVE-2025-8000: Ashlar-Vellum Cobalt · Type Confusion

Affects Ashlar-Vellum CobaltSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

AI-suggested

1. Immediate mitigation should focus on user awareness and training to avoid opening LI files from untrusted or unknown sources. 2. Implement strict email filtering and attachment scanning to detect and block suspicious LI files before reaching end users. 3. Employ endpoint protection solutions capable of detecting anomalous behavior related to Ashlar-Vellum Cobalt processes. 4. Restrict user privileges to the minimum necessary to run Ashlar-Vellum Cobalt, limiting the impact of potential code execution. 5. Monitor network and host logs for unusual activity indicative of exploitation attempts, such as unexpected process launches or file modifications. 6. Coordinate with Ashlar-Vellum for timely updates or patches and plan for rapid deployment once available. 7. Consider sandboxing or isolating the application environment to contain potential exploits. 8. Review and tighten file sharing policies, especially for LI files, to reduce exposure to malicious inputs. These targeted measures go beyond generic advice by focusing on the specific attack vector (LI file parsing) and the operational context of Ashlar-Vellum Cobalt.

Description

Ashlar-Vellum Cobalt LI File Parsing Type Confusion Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Ashlar-Vellum Cobalt. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of LI files. The issue results from the lack of proper validation of user-supplied data, which can result in a type confusion condition. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-26051.

References

Community reviews

Loading reviews…