---
id: CVE-2026-19547
title: >-
  Ghostscript for Windows is vulnerable to local privilege escalation through
  PostScript resource file hijacking
summary: >-
  Ghostscript for Windows is vulnerable to local privilege escalation through
  PostScript resource file hijacking. Due to the application searching for
  PostScript resource files in predictable paths under C:\\gs\\ that do not
  exist by defau…
severity: high
cvss: 7
cvssVector: 'CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N'
cwe:
  - CWE-426
vendor: Artifex Software Inc.
product: Ghostscript
affected:
  - Ghostscript < 10.08.0
published: '2026-09-29'
updated: '2026-09-29'
sourceUpdated: '2026-09-29T11:16:42.730'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-19547'
references:
  - url: 'https://bugs.ghostscript.com/show_bug.cgi?id=709522'
    label: cvd@cert.pl
  - url: 'https://cert.pl/en/posts/2026/09/CVE-2026-19547'
    label: cvd@cert.pl
  - url: 'https://ghostscript.com/'
    label: cvd@cert.pl
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-09-29T10:52:13.510348Z'
cvssSource: cna
ingestedAt: '2026-09-29T10:31:36.310Z'
---

## Overview

Ghostscript for Windows is vulnerable to local privilege escalation through PostScript resource file hijacking. Due to the application searching for PostScript resource files in predictable paths under C:\\gs\\ that do not exist by default on Windows installations, combined with Windows default ACLs allowing any authenticated user to create directories at the root of C:\\, an attacker who is an authenticated local user can create the expected directory structure and plant a malicious PostScript file. When any user or service subsequently runs Ghostscript, the planted file is automatically loaded and executed with the full privileges of the Ghostscript process. This results in full compromise of Ghostscript process context, as well as running arbitrary code on the machine with Ghostscript process privileges.


This issue was fixed in version 10.08.0.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.