CVE-2025-65088
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 · uneditedAn Out-of-Bounds Read vulnerability is present in Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, and Cobalt Share versions 12.6.1204.216 and prior that could allow an attacker to disclose information or execute arbitrary code when a specially crafted VC6 file is being parsed.
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 confidenceAn Out-of-Bounds Read vulnerability exists in multiple Ashlar-Vellum CAD software products (Cobalt, Xenon, Argon, Lithium, and Cobalt Share) when parsing specially crafted VC6 files. This memory safety flaw can be exploited to disclose sensitive information from process memory or achieve arbitrary code execution on the targeted system.
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<= 12.6.1204.216<= 12.6.1204.216<= 12.6.1204.216<= 12.6.1204.216<= 12.6.1204.216CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Ashlar-Vellum CAD productsSearch system for installed Ashlar applications. On Windows, check Add/Remove Programs or look in Program Files for folders named Ashlar, Argon, Cobalt, Lithium, or Xenon. On macOS, check /Applications for Ashlar applications.Affected if Any of the five affected products (Argon, Cobalt, Cobalt Share, Lithium, Xenon) are installed on the system
-
Determine the installed version numberFor each installed Ashlar product, locate the executable and check its version: on Windows, right-click the main .exe file, select Properties, then look at the Details tab for Product Version; on macOS, right-click the app, select Get Info, and check the Version field.Affected if The displayed version is 12.6.1204.216 or any lower version number
-
Confirm the software includes VC6 file handlingAttempt to open or import a VC6 format file within the installed Ashlar application, or check the application's supported file formats list (typically found under File > Open or File > Import menus).Affected if The software can parse or import .vc6 files (this is a built-in capability in affected versions)
-
Compare against affected version rangeCompare your confirmed installed version to the affected range: versions 12.6.1204.216 and below are vulnerable. If your version matches or is lower, you are within the affected range.Affected if Installed version is 12.6.1204.216 or lower
If any Ashlar-Vellum product (Argon, Cobalt, Cobalt Share, Lithium, Xenon) is installed at version 12.6.1204.216 or lower and supports VC6 file parsing, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of the affected software when available; avoid opening untrusted or specially crafted VC6 files from unknown sources until the vulnerability is remediated.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65088 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-65088 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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