dbcve.org
ArgonApplication · Ashlar

CVE-2025-52584

HIGH · 7.8 CVSS v3.1 Published 2025-08-18
Fix available
A fix is available. Upgrade to 12.2.1204.204 or later.
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
In Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, and Cobalt Share versions prior to 12.6.1204.204, the affected applications lack proper validation of user-supplied data when parsing XE files. This could lead to a heap-based buffer overflow. An attacker could leverage this vulnerability to execute arbitrary code in the context of the current process.

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 · high confidence

Heap-based buffer overflow in Ashlar-Vellum CAD software (Cobalt, Xenon, Argon, Lithium) due to lack of proper validation of user-supplied data when parsing malicious XE files. Successful exploitation allows arbitrary code execution in the context of the current process.

MitigationUpgrade to version 12.6.1204.204 or later. Until patched, avoid opening untrusted XE files from unknown or untrusted sources.

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
ArgonApplication
Affected:< 12.2.1204.204
CobaltApplication
Affected:< 12.2.1204.204
Cobalt ShareApplication
Affected:< 12.2.1204.204
LithiumApplication
Affected:< 12.2.1204.204
XenonApplication
Affected:< 12.2.1204.204

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.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 checks

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

  1. Identify installed Ashlar product
    Check Program Files or Program Files (x86) for Ashlar-Vellum folder. Look for Cobalt, Xenon, Argon, Lithium, or Cobalt Share in the application name. The product name appears in Add/Remove Programs or in the application's title bar when launched.
    Affected if Any of the five products (Argon, Cobalt, Cobalt Share, Lithium, Xenon) is installed
  2. Determine product version
    Right-click the executable (e.g., Cobalt.exe, Xenon.exe) in the installation folder, select Properties, then look at the Details tab for File Version. Alternatively, open the application and check Help > About.
    Affected if Version is less than 12.2.1204.204
  3. Confirm XE file handling capability
    Open the application and attempt to open or import a file with .xe extension. Check File > Open or File > Import dialogs for XE file type support.
    Affected if The application can open or import .xe files
  4. Verify XE parser is enabled by default
    Launch the application with default settings. The XE file parser is built into the core functionality and does not require a separate module to be enabled.
    Affected if Default installation with XE file support active

You are affected if any Ashlar-Vellum product (Argon, Cobalt, Cobalt Share, Lithium, or Xenon) is installed with a version lower than 12.2.1204.204 and can process XE files.

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.

dbcve · scoped
Upgrade available Upgrade to 12.2.1204.204 or later
Fixed in 12.2.1204.204
Interim mitigation

Upgrade to version 12.6.1204.204 or later. Until patched, avoid opening untrusted XE files from unknown or untrusted sources.

Recommended fix Moderate confidence

Version 12.6.1204.204 or later

  1. 1. Identify the current installed version of the Ashlar-Vellum software (Argon, Cobalt, Cobalt Share, Lithium, or Xenon)
  2. 2. Obtain version 12.6.1204.204 or later from the official Ashlar-Vellum vendor
  3. 3. Back up all existing projects and configuration data
  4. 4. Apply the upgrade following the vendor's standard installation procedures
  5. 5. Verify the installation was successful by checking the updated version number
Caveat Review release notes for any compatibility changes or feature modifications before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Argon Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-52584 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