Ghostscript sandbox escape reaches apps via file uploads
A patched Ghostscript flaw, CVE-2026-125396, let crafted files run commands through upload and print features. Update the renderer your apps actually use.

A flaw in Ghostscript, the interpreter many Linux servers use to turn uploaded PDFs, PostScript and images into other formats, lets a crafted file escape the program’s sandbox and run commands on the server that processes it. It is patched, and The Hacker News reports no attacks using it have been seen. The interesting part is how little an application has to do to be exposed.
What was found
The bug, tracked as CVE-2026-125396, is a use-after-free in the part of Ghostscript that loads fonts. A crafted document can use it to switch off the checks in -dSAFER, the sandbox meant to stop a document from running commands or reaching files. Artifex, which develops Ghostscript, fixed it in version 10.08.0 on September 8. The CVE was published last week.
The security firm pwn.ai showed that about ten common applications could be made to hand such a file to Ghostscript through ordinary upload, preview and print features. Each demonstration ran a command as the low-privilege account that does the rendering. We are not describing the file or the steps, and the firm’s own write-up is the place for the per-application detail.
Several paths needed no login, according to the report:
- an anonymous print job to a shared Debian 13 queue
- an emailed attachment that Roundcube webmail processed when the recipient opened the message
- public upload forms in the WordPress plugins Forminator and Essential Addons for Elementor
WordPress Core needed more: an account that can upload files, which Authors and higher roles have by default. WordPress had already closed its own upload path in version 7.0.4 on August 12 under a separate identifier, CVE-2026-65640. That fix and the Ghostscript fix cover different points in the same chain, so one does not replace the other.
Why apps are exposed without calling it
Applications often never call Ghostscript directly. Image and document libraries such as ImageMagick, Pillow, libvips or a Qt plugin pass PostScript or EPS content to it, even when the file is named .png, .jpg or .pdf. A thumbnail or a crop can start the interpreter. The CVE is classed as a local flaw, but the firm’s tests reached Ghostscript over the network through print jobs, email and web uploads.
What to do
Update to Ghostscript 10.08.0 or later, and make sure the update lands where the renderer actually runs. A host package upgrade does not touch a separate copy bundled in a container image or an application, so a document worker can keep running old code. Check those images.
Distribution coverage is uneven. As of last week, the firm’s survey listed:
- Debian 12 (Bookworm): vulnerable
- Amazon Linux 2, 2023 and 2027 Preview: fix pending
- SUSE Linux Enterprise 12 SP5 and parts of 15, plus SLES 16.0 and 16.1: fix in progress
- openSUSE Leap 16.0 and 16.1: affected
That list records package status, not a tested attack path for each system. The firm did not establish whether current Red Hat, Rocky Linux, AlmaLinux, Oracle Linux or stable Fedora packages carry the fix. Until the renderer is updated, the report suggests reducing exposure by requiring authentication on upload and print paths.
Analysis
Artifex’s Ken Sharp described the vulnerable internal step as “an ancient piece of code well known to be a vulnerability, but difficult to eradicate”, and the project is moving it into safer code. That is a slow fix for a component that sits behind so many features nobody thinks of as “running Ghostscript”. The same mistake, different decade: a quiet dependency in the upload path inherits the trust of everything in front of it.
For other library-level fixes this week, see our coverage of the GPGME double free and the 2.3.1 update and the Ruby patches.
Found this useful? Share it.


