{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-7981 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-7981 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-7981 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."},"fix_prompt":"Check this codebase for CVE-2025-7981 and fix it if it is affected.\n\nWhat it is: CVE-2025-7981 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.\nExploitation: There is no known exploitation of CVE-2025-7981 in the wild and no public exploit code.\n\nAffected product: Ashlar-Vellum Graphite. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-7981/ (Markdown: https://insights.sbomify.com/CVE-2025-7981/index.md)","id":"CVE-2025-7981","markdown":"https://insights.sbomify.com/CVE-2025-7981/index.md","name":"CVE-2025-7981","record":{"aliases":["GHSA-pgj4-x59p-fp49"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ashlar-Vellum Graphite","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening malicious VC6 files in Ashlar-Vellum Graphite due to uninitialized memory usage.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"graphite","vendor":"ashlar"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-457","name":"Use of Uninitialized Variable"}],"description":"Ashlar-Vellum Graphite VC6 File Parsing Uninitialized Variable 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.\n\nThe specific flaw exists within the parsing of VC6 files. The issue results from the lack of proper initialization of memory prior to accessing it. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-25475.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Ashlar-Vellum Graphite VC6 File Parsing Uninitialized Variable Remote Code Execution Vulnerability","id":"CVE-2025-7981","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Ashlar-Vellum Cobalt LI File Parsing Integer Overflow Remote Code Execution Vulnerability","id":"CVE-2025-7982"},"packages":[],"prev":{"headline":"Ashlar-Vellum Graphite VC6 File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability","id":"CVE-2025-7980"},"products":["Graphite"],"published":"2025-09-17","related":[{"cvss_score":7.8,"headline":"Ashlar-Vellum Graphite VC6 File Parsing Uninitialized Variable Remote Code Execution Vulnerability","id":"CVE-2025-7978","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":7.8,"headline":"Ashlar-Vellum Graphite VC6 File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability","id":"CVE-2025-7979","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":7.8,"headline":"Ashlar-Vellum Graphite VC6 File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability","id":"CVE-2025-7980","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":7.8,"headline":"Ashlar-Vellum Graphite VC6 File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability","id":"CVE-2025-7983","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":7.8,"headline":"Ashlar-Vellum Graphite VC6 File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability","id":"CVE-2025-7986","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":7.8,"headline":"Ashlar-Vellum Graphite VC6 File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability","id":"CVE-2025-7987","kev_date_added":null,"published":"2025-09-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-09-18","vendors":["Ashlar-Vellum"]},"summary":"Remote attackers can execute arbitrary code by tricking users into opening malicious VC6 files in Ashlar-Vellum Graphite due to uninitialized memory usage.","url":"https://insights.sbomify.com/CVE-2025-7981/"}