- pwn.ai showed that a crafted file could escape Ghostscript's sandbox and run commands. Its confirmed cases include Roundcube, Plesk, MediaWiki, DokuWiki and WordPress plugins. The flaw is CVE-2026-125396.
- Ghostscript 10.08.0 fixed it on September 8. A host update does not reach a separate copy bundled in a container, and The Hacker News says distribution coverage is uneven.
- Leaders should ask which Ghostscript copies their systems run and who can send them files. The Hacker News says there have been no reports of attacks.
The risk sits in a tool nobody bought
Most companies can name the software they chose. Few can name the software that software quietly calls. A thumbnail on an upload form, a preview in webmail or a shared office printer may each start a program nobody installed on purpose.
That is the lesson of Upload2Shell, research from the security firm pwn.ai. The weak spot was not a product the affected firms had bought. It was Ghostscript, a program that reads PDF and PostScript files and runs underneath other tools.
What pwn.ai found
The bug sits in how Ghostscript loads Type 1 fonts, a font format used inside documents. pwn.ai classes it as a use-after-free. That is a memory error. The program keeps using a piece of memory after giving it back.
The firm says a crafted document can exploit this to cross the -dSAFER boundary. That boundary is the sandbox meant to stop a document from running commands. Past it, the attacker's commands run with the rights of the rendering process.
The flaw is CVE-2026-125396. The Hacker News gives it a score of 8.5 out of 10 in the advisory. That outlet reports that no attacks exploiting it have surfaced so far.
Why a .png can reach a PostScript interpreter
An application does not need to call Ghostscript itself. Image libraries are the usual go-between. The Hacker News names ImageMagick, Pillow, libvips and a Qt plugin as tools that can forward PostScript-style content to Ghostscript. This can happen even when the upload is named .png, .jpg or .pdf.
So the file's name does not settle the route. What the file contains can. A routine step like a thumbnail or a crop can wake the interpreter.
In the Roundcube test, pwn.ai says an ImageMagick delegate ran the proof. A delegate is a helper program that the library hands work to. Here, that helper was Ghostscript.
The Hacker News says pwn.ai fed such a file through about ten applications. That count comes from the outlet. pwn.ai's own timeline lists confirmed command execution in Roundcube, Plesk's bundled Roundcube path, MediaWiki, DokuWiki, Mayan EDMS and two WordPress plugins. Some of these share a component.
Several paths needed no login. One was an anonymous print job to a shared queue on Debian 13, where the command ran as the user lp. Another was an email attachment that Roundcube processed when the message was opened. A third was a public upload form in the Forminator and Essential Addons for Elementor plugins.
WordPress Core needed more. An attacker first needs an account allowed to upload files. The Hacker News notes that Authors and higher roles hold that right by default. The CVE carries a local classification. Yet pwn.ai's demonstrations arrived over print jobs, email and web uploads, according to The Hacker News.
Two fixes, and a timeline that matters
The application fixes came first. WordPress closed its upload path on August 12 under CVE-2026-65640. The Hacker News puts that fix in WordPress 7.0.4. It landed almost four weeks before the Ghostscript fix, and months before the Ghostscript flaw had a CVE ID.
Artifex, the company behind Ghostscript, shipped version 10.08.0 on September 8. The CVE ID came on November 9. The Hacker News quotes developer Ken Sharp calling the weak step "an ancient piece of code well known to be a vulnerability, but difficult to eradicate."
Roundcube also acted. Its fix blocks unsafe attachment image types before ImageMagick converts them, under CVE-2026-114727. These patches guard different points on one path. Installing one does not replace the other.
Distribution patching is uneven
Debian's fixed build for version 13 is 10.05.1~dfsg-1+deb13u3, published October 10. pwn.ai says Debian's first stable-security update came on September 25. Ubuntu issued fixed packages for seven releases on October 21 under USN-8949-1.
That is not the whole picture. The Hacker News reports that coverage across distributions is uneven. In pwn.ai's survey, as the outlet relays it, several distributions still shipped a vulnerable build or had a fix pending a week ago.
The survey left the fix status of current Red Hat, Rocky Linux, AlmaLinux, Oracle Linux and stable Fedora packages open. Treat those systems as unconfirmed until you check.
Why the host patch may not be enough
The Hacker News raises a point for anyone running containers. A container image can carry its own Ghostscript. Patching the host operating system leaves that copy alone.
The same holds for an application that ships its own bundle. A background service that converts documents can keep running the vulnerable copy even after the host's own package is updated.
Here is the idea worth keeping. A report that says "servers updated" answers a question about packages. It does not say where the interpreter actually runs. pwn.ai adds that another print filter, thumbnailer or preview may be the next way in.
What to ask your team
Start with a list. Which systems open files that come from outside the company? Think of upload forms, webmail, document inboxes and print servers.
Then ask which Ghostscript version each one really runs. Include copies inside container images. Ask who can send each system a file, and whether that needs a login.
The Hacker News names stopgaps until the renderer is updated. Require login on print queues. Limit the file types an image processor accepts. Add system controls. In one test, an AppArmor profile kept the compromised interpreter from starting a shell.
Finally, ask vendors which renderer sits behind their preview features. If they cannot say, record that as an open item, not as a clean result.
A file named .png is only a claim about itself. The real question is what opens it next.
Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: pwn.ai.





