CVE-2025-7987
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 · uneditedAshlar-Vellum Graphite VC6 File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Ashlar-Vellum Graphite. 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 VC6 files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-25756.
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 confidenceThe vulnerability exists in the VC6 file parser of Ashlar-Vellum Graphite. Due to insufficient validation of user-supplied data during file parsing, an out-of-bounds write occurs past the end of an allocated buffer. Attackers can exploit this by enticing users to open malicious VC6 files, achieving code execution in the context of the current process.
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= 13.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Ashlar Graphite is installedCheck for Ashlar Graphite application in program files or list installed programs. On Windows, check C:\Program Files\Ashlar or C:\Program Files (x86)\Ashlar directories, or use 'Get-ItemProperty' on registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for program entries containing 'Ashlar' or 'Graphite'.Affected if The application is not installed or cannot be found.
-
Verify installed version is 13.0Locate the Graphite executable (typically Graphite.exe) and check its file version. In Windows, right-click the executable > Properties > Details > File Version, or use PowerShell: (Get-Item 'C:\Program Files\Ashlar\Graphite\Graphite.exe').VersionInfo.FileVersion.Affected if The installed version is exactly 13.0, placing it within the affected range.
-
Confirm VC6 file parser functionality is presentCheck if the Graphite installation includes VC6 import/parser modules. Look for files related to VC6 parsing in the application directory, or attempt to determine if VC6 file import capability exists in the installed build.Affected if VC6 file parsing capability exists in the installation and the application can open .vc6 files.
-
Check for presence of untrusted VC6 filesScan local directories for .vc6 files, particularly in downloads, recent documents, or file transfer locations. Use file system search for *.vc6 extension.Affected if Untrusted or unverified VC6 files are present and could be opened by the application.
You are affected if Ashlar Graphite version 13.0 is installed with VC6 file parsing capability and users may open untrusted VC6 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 dataAvoid opening untrusted VC6 files from unknown sources. Apply vendor patches when available and implement file quarantine/sandboxing for untrusted file processing until the patch is deployed.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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 $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7987 — 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-7987 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