CVE-2025-65084
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 Write 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 confidenceAn out-of-bounds write vulnerability in Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, and Cobalt Share (versions 12.6.1204.216 and prior) allows memory corruption, potentially enabling information disclosure or arbitrary code execution via crafted inputs.
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.
-
Identify installed Ashlar-Vellum productsCheck common installation directories (C:\Program Files\Ashlar or C:\Program Files (x86)\Ashlar on Windows, /Applications/Ashlar on macOS) or use system package managers to list installed software containing 'Ashlar', 'Cobalt', 'Argon', 'Lithium', or 'Xenon'Affected if Any of the five products (Argon, Cobalt, Cobalt Share, Lithium, Xenon) are present on the system
-
Determine installed product versionFor Windows, check the executable's properties (right-click the .exe, view Details/Version tab) or run 'Get-ItemProperty' on the main .exe in Program Files. For macOS, right-click the .app bundle and select Get Info to view version. Compare against 12.2.1204.207 and 12.6.1204.216Affected if Installed version is 12.2.1204.207 or lower, or 12.6.1204.216 or lower (the summary indicates versions through 12.6.1204.216 are affected)
-
Verify the product processes external inputThe vulnerability is triggered via crafted inputs. Determine if the software is used to open files from untrusted sources, network locations, or external users. Check recent file open dialogs, default file associations, or configured import pathsAffected if The software routinely opens CAD files, designs, or other documents from untrusted or external sources without prior validation
A system is affected if any Ashlar-Vellum product (Argon, Cobalt, Cobalt Share, Lithium, Xenon) is installed with a version at or below 12.2.1204.207 (or 12.6.1204.216 per the summary) and processes untrusted input 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 dataUpdate to a version beyond 12.6.1204.216 once the vendor releases a patch, or minimize exposure by restricting access to untrusted files and network inputs.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65084 — 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-65084 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