# CVE-2025-7983: Ashlar-Vellum Graphite VC6 File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code by tricking users into opening a malicious VC6 file in Ashlar-Vellum Graphite due to a heap-based buffer overflow.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2025
- **Updated:** 18 Sep 2025
- **Also known as:** GHSA-cj75-2q24-r493

## What is CVE-2025-7983?

CVE-2025-7983 is a high-severity memory corruption vulnerability in Ashlar-Vellum Graphite, published on 17 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Ashlar-Vellum Graphite VC6 File Parsing Heap-based Buffer Overflow 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 the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-25477.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-7983?

It affects 1 product.


Products: Ashlar Graphite.

## How do I fix CVE-2025-7983?

No fix has been published for CVE-2025-7983 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-7983 being exploited?

There is no known exploitation of CVE-2025-7983 in the wild and no public exploit code.

## Other vulnerabilities in Ashlar-Vellum Graphite

- [CVE-2025-7978](https://insights.sbomify.com/CVE-2025-7978/): Ashlar-Vellum Graphite VC6 File Parsing Uninitialized Variable Remote Code Execution Vulnerability (high 7.8)
- [CVE-2025-7979](https://insights.sbomify.com/CVE-2025-7979/): Ashlar-Vellum Graphite VC6 File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 7.8)
- [CVE-2025-7980](https://insights.sbomify.com/CVE-2025-7980/): Ashlar-Vellum Graphite VC6 File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability (high 7.8)
- [CVE-2025-7981](https://insights.sbomify.com/CVE-2025-7981/): Ashlar-Vellum Graphite VC6 File Parsing Uninitialized Variable Remote Code Execution Vulnerability (high 7.8)
- [CVE-2025-7986](https://insights.sbomify.com/CVE-2025-7986/): Ashlar-Vellum Graphite VC6 File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7983 and fix it if it is affected.

What it is: CVE-2025-7983 is a high-severity memory corruption vulnerability in Ashlar-Vellum Graphite, published on 17 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-7983 in the wild and no public exploit code.

Affected product: Ashlar-Vellum Graphite. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-7983/ (Markdown: https://insights.sbomify.com/CVE-2025-7983/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7983
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7983
- OSV: https://osv.dev/vulnerability/CVE-2025-7983

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-7983/
Summaries are generated and may contain mistakes; the official description above is the record.