CobaltApplication · Ashlar

CVE-2025-7989

HIGH · 7.8 CVSS v3.0 Published 2025-09-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Ashlar-Vellum Cobalt AR File Parsing Out-Of-Bounds Read 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 AR files. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated data structure. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-25943.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An out-of-bounds read vulnerability exists in Ashlar-Vellum Cobalt's AR file parser due to insufficient validation of user-supplied data. The lack of proper bounds checking allows reading past the end of an allocated data structure, which can be leveraged to achieve remote code execution in the context of the current process.

MitigationAvoid opening untrusted or malicious AR files. Apply vendor-provided security updates for Ashlar-Vellum Cobalt once available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CobaltApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Ashlar Cobalt installation
    Check for Ashlar Cobalt in installed programs (Windows: Add/Remove Programs, Program Files; macOS: /Applications; Linux: package manager or /opt). Search for files named 'Cobalt', 'Ashlar', or executables like cobalt.exe, ashlar.exe.
    Affected if Ashlar Cobalt software is found on the system
  2. Confirm AR file handler is active
    Check if AR file extension association exists. On Windows, search registry under HKCR\.ar or look for file associations. On systems with Cobalt, check if AR files can be opened or if the AR parser module loads.
    Affected if AR file parsing capability is enabled or AR files can be opened by the software
  3. Identify version for inventory
    Launch Ashlar Cobalt and navigate to Help > About, or right-click the executable and select Properties > Details to view version information. If version cannot be determined, note that all versions are affected.
    Affected if Any version of Ashlar Cobalt is installed (all versions are affected)
  4. Audit recent AR file access
    Review recent file access logs, document repositories, or the application's recent files list for .ar file activity. Check temp directories for recently processed AR files.
    Affected if AR files have been opened or processed by the software

The environment is affected if Ashlar Cobalt is installed and can process AR files, since the vulnerability exists in the AR file parser for all versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid opening untrusted or malicious AR files. Apply vendor-provided security updates for Ashlar-Vellum Cobalt once available.

Fix this in Cobalt Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7989 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7989 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data