CVE-2025-65085
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 · uneditedA Heap-based Buffer Overflow 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.
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 confidenceA heap-based buffer overflow vulnerability in Ashlar-Vellum CAD software (Cobalt, Xenon, Argon, Lithium, and Cobalt Share) versions 12.6.1204.216 and prior could allow remote attackers to disclose sensitive information or execute arbitrary code via specially crafted files or network interactions.
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.2.1204.207<= 12.2.1204.207<= 12.2.1204.207<= 12.2.1204.207<= 12.2.1204.207CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
List installed Ashlar-Vellum applicationsCheck Program Files or Program Files (x86) folders for Ashlar-Vellum directories, or use system inventory tools to find Ashlar Cobalt, Xenon, Argon, Lithium, or Cobalt Share installationsAffected if Any of these five products are found on the system
-
Determine installed version of Ashlar softwareOpen the application, then navigate to Help > About or use the application's version information dialog. Alternatively, check the executable file properties (right-click the .exe file > Properties > Details)Affected if The displayed version is 12.2.1204.207 or earlier, or 12.6.1204.216 or earlier
-
Compare version against affected rangesFor Argon, Cobalt, Cobalt Share, Lithium, or Xenon: compare your installed version to <= 12.2.1204.207. For any Ashlar-Vellum CAD product: compare to <= 12.6.1204.216Affected if Your installed version falls within or below these version numbers
-
Identify file association handlingCheck if the CAD application is configured to auto-open files or if users routinely open CAD files from untrusted sources. Review file type associations for .cobalt, .xenon, .argon, .lithium extensionsAffected if Users can be tricked into opening maliciously crafted CAD files, making the buffer overflow exploitable
If any Ashlar-Vellum CAD product is installed at version 12.2.1204.207 or prior (or 12.6.1204.216 or prior), the environment is vulnerable and can be exploited by opening specially crafted files.
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 dataUpgrade to a vendor-patched version newer than 12.6.1204.216; until then, restrict exposure to untrusted CAD files and network vectors, and monitor for indicators of compromise.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65085 — 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-65085 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