Skip to main content

Ghostscript Flaw Fixed in September Now Shown Running Commands Through Upload Forms, Webmail and Print Queues

pwn.ai has shown how CVE-2026-125396, a Ghostscript sandbox escape fixed on 8 September, can be reached through thumbnails, webmail attachments and print jobs. No attacks are reported. What to check, and why updating the host is not enough.

KBY News Desk10 min read
Close-up of a modern printer with a touchscreen interface in a professional office setting.

A flaw in Ghostscript that its maintainers fixed on 8 September is now the subject of public research showing how it can be reached through features most administrators never think of as “running Ghostscript”: a thumbnail generated for an uploaded image, a webmail message opened by its recipient, an anonymous print job. The security firm pwn.ai published an evidence index on its Upload2Shell page, and The Hacker News reported on Sunday 22 November that the firm had demonstrated command execution through about ten common applications. The flaw is tracked as CVE-2026-125396. There are no reports of it being used in real attacks, and a fixed version, Ghostscript 10.08.0, has been available for more than two months. The problem is not the fix. It is working out which of your systems still run an old copy.

Ghostscript is the interpreter many Linux servers use to turn PDFs, PostScript and other files into images or other formats. Applications often reach it without calling it. According to The Hacker News, image and document libraries such as ImageMagick, Pillow, libvips or a Qt plugin will hand PostScript or EPS content to Ghostscript to render, even when the file is named .png, .jpg or .pdf. That is why a routine feature, such as making a thumbnail or cropping a picture, can start the interpreter.

#What the flaw is, and what it needs

The bug is a use-after-free, a memory error where a program keeps using memory it has already released, in the part of Ghostscript that loads fonts. Ghostscript normally runs documents inside a sandbox switched on with the -dSAFER option, which is meant to stop a document from running commands or reaching files. A crafted document uses the bug to switch those checks off, according to The Hacker News. The VulnCheck advisory describes the mechanism more precisely: a procedure in Ghostscript’s gs_fonts.ps file calls a privileged operator without checking the types of what it is given, so a crafted PostScript or PDF document can trigger a type error, recover that operator through a custom error handler and then cause the use-after-free to run arbitrary code. VulnCheck lists every release before 10.08.0 as affected and gives the flaw a CVSS 4.0 score of 8.5.

The score is a little lower than the headline would suggest because of how the flaw is classified. VulnCheck’s vector marks the attack as local and requiring user interaction, and The Hacker News notes that the CVE is classed as a local flaw. pwn.ai’s tests, however, reached Ghostscript from the network through print jobs, email and web uploads. We read that as the real lesson: a “local” rating on a library tells you about the library, not about how your applications feed it files.

What an attacker gets is limited to what the rendering process can do. The Hacker News reports that in the firm’s tests a command ran each time as the low-privilege account that does the rendering. That is still a foothold on a server, and on a web server it is the account that can often read the site’s files and configuration, but it is not administrator control by itself.

#Where pwn.ai says it got through

The pwn.ai evidence index lists applications where the firm says it observed a command running, with the access each one needed. We have taken the details from that page and from The Hacker News report; the firm’s own test conditions matter, so we give them rather than a general claim.

  • Debian 13 with CUPS: an anonymous print job sent to a shared network queue ran a command on the host as the lp user.
  • Roundcube webmail 1.7.2: an attachment from an external sender was thumbnailed when the recipient viewed the message, and ran a command as www-data without any click on the attachment. The firm notes this needed a tested ImageMagick delegate to be configured.
  • WordPress plugins: public forms in Forminator (a PDF form configured to store files in the Media Library) and in Essential Addons for Elementor (a login and register widget with an upload field enabled) ran commands with no login, five times out of five in the firm’s trials.
  • MediaWiki, DokuWiki, Mayan EDMS and ResourceSpace: each ran a command in the firm’s tests through anonymous or authenticated upload, resize or email-import paths, depending on how the site was configured.
  • WordPress Core: needs an account with the upload capability, which Authors and above have by default, on a site using Imagick and Ghostscript.
  • Plesk Obsidian: command execution in the Roundcube thumbnail path it ships, on a bundled Ghostscript 9.54.0. The firm adds that an enforced AppArmor profile blocked the shell in its test, and that it did not test a deployed endpoint.

The firm also lists several applications, among them Gradio, InvokeAI, ComfyUI and Paperless-ngx, as routes it mapped through their source code. For Gradio it records only that Ghostscript was started when an image was submitted, not that a command ran. It separates the two groups, and so should anyone reading the list: a mapped path is a place to look, not a confirmed attack. It reports that Google fixed the affected path in its own image and document processing on 10 November. The Hacker News adds that pwn.ai’s reports of similar problems at Dropbox and other unnamed services are separate Ghostscript bugs, not this one.

#The WordPress half of the chain

WordPress had already acted. Its 7.0.4 security release, on 12 August, fixed what it described as authenticated Author-or-higher remote code execution through a malicious file upload on sites that use Imagick and Ghostscript, credited to pwn.ai and tracked as CVE-2026-65640. The Hacker News makes the point that matters for administrators: that fix and the Ghostscript fix cover different points in the same chain, so updating one does not remove the need for the other. A site on WordPress 7.0.4 with an old Ghostscript behind it has closed one route, not the flaw.

#Fixed versions and who still needs to act

Artifex, which develops Ghostscript, released 10.08.0 on 8 September. The Hacker News quotes the developer who handled the fix, Ken Sharp, describing the vulnerable step as “an ancient piece of code well known to be a vulnerability, but difficult to eradicate”, and says the project is moving that step into safer code. Distributions have backported the fix rather than moving to 10.08.0. pwn.ai says Debian published 10.05.1~dfsg-1+deb13u3 as the Debian 13 security build now marked fixed, and that Ubuntu released fixed packages for seven releases on 21 October in USN-8949-1. Roundcube restricted unsafe attachment image types before ImageMagick conversion on 19 October, under CVE-2026-114727.

Coverage elsewhere is uneven. The Hacker News relays pwn.ai’s package survey, taken about a week before the article: Debian 12 listed as vulnerable; Amazon Linux 2, 2023 and the 2027 preview with a fix pending; SUSE Linux Enterprise 12 SP5, parts of 15 and SLES 16.0 and 16.1 with a fix in progress; openSUSE Leap 16.0 and 16.1 affected. The firm did not establish whether current Red Hat, Rocky Linux, AlmaLinux, Oracle Linux or stable Fedora packages carry the fix. That status will have moved since, so check your own distribution’s tracker rather than relying on a week-old list.

#Our view: a patch problem that is really an inventory problem

We do not think this is an emergency for most organisations, and we would not tell anyone to drop everything. There is no sign of exploitation, the file has to reach Ghostscript, and the result is code running as an unprivileged account. We do think it deserves a prompt, short piece of work for anyone with a public upload form, a webmail server or a shared print server, because those are the places where a stranger can supply the file.

The hard part is that Ghostscript is a hidden dependency. Updating the host operating system does not update a separate copy bundled inside a container image or an application, so a document worker can keep running the old code after the host package is replaced, as The Hacker News points out. Our reading is that the number of vulnerable systems will therefore be larger than any package audit suggests, and that the exposed copies will mostly be the ones nobody remembers installing. We expect more application-specific write-ups from pwn.ai, since its page says case studies and proofs will be linked as they are published. What would prove us wrong is a confirmed exploitation report, which would move this from “fix this week” to “fix today” for anything with a public upload path.

#What to check, in order

  1. Find every Ghostscript. On each Linux server that handles uploads, mail or printing, run gs --version and check the package with your distribution’s tool. A distribution may show an old version number with the fix backported, so compare the package build against your vendor’s security notice, not only the number. The Debian 13 and Ubuntu builds above are examples.
  2. Look inside containers. Run the same version check inside each image that processes documents or images, and rebuild images from a patched base. The host’s package manager will not touch them.
  3. Update the applications that call it. WordPress 7.0.4 or later, a current Roundcube, and the vendors of Forminator and Essential Addons for Elementor for their own fix status. We could not confirm from the sources we read whether either plugin has shipped a fix.
  4. Reduce what reaches it while you wait. The Hacker News reports that exposure can be reduced by requiring authentication on print queues and by limiting which file types an image processor accepts. Limiting ImageMagick’s handling of PostScript, EPS and PDF is a common hardening step; check your ImageMagick version’s own documentation before changing its policy file, because some sites need those formats.
  5. Check the account it runs as. The worker that renders files should be a low-privilege account with little access to the rest of the server. pwn.ai saw a mandatory-access-control profile (AppArmor) stop a shell in one of its tests, which is a useful reminder that containment is worth having.

#If you run a small business website

If your firm’s site is on WordPress, check two things this week: that WordPress itself is on 7.0.4 or later, and whether any form on the site lets visitors upload files without logging in. A contact form that accepts attachments is the example. If you use a hosting provider or web agency, ask them one question, word for word: “Is the file-processing software on our server, including Ghostscript, up to date, and do any of our public forms accept uploaded files?” A managed host may already have patched the server; the question is whether anyone has checked. Our small business section covers IT basics for firms with no IT team.

#What is not known

The sources do not say how many internet-facing systems are exposed, which of the listed applications have shipped their own fixes, or whether any attacker is using the bug. The Hacker News notes that the published proof-of-concept file shows only the core memory trick and fails on patched 10.08.0. pwn.ai says further case studies are to come. We will update this story if exploitation is reported, if more vendors publish fixes, or if the distribution picture changes. Our recent coverage of two other open-source flaws that servers carry without anyone choosing them: the Ruby memory bugs and the Linux kernel NoisyTCP flaw.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01The Hacker News: Researchers Demonstrate Ghostscript Sandbox-Escape RCE via Crafted File Uploads in Popular Appsthehackernews.com
  2. 02pwn.ai: Upload2Shell, CVE-2026-125396 (disclosure timeline and evidence index)pwn.ai
  3. 03VulnCheck advisory: Ghostscript before 10.08.0 -dSAFER bypassvulncheck.com
  4. 04WordPress.org: WordPress 7.0.4 releasewordpress.org

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on Ghostscript Flaw Fixed in September Now Shown Running Commands Through Upload Forms, Webmail and Print Queues. Comments are checked for spam and held for moderation before appearing.

Loading comments...

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.