SAASMENT

News

A crafted file can escape Ghostscript and run a command.

A flaw in Ghostscript, CVE-2026-125396, lets a crafted file turn off the program's sandbox and run commands on the server that converts it. Artifex fixed it in Ghostscript 10.08.0 on September 8. The report says there have been no attacks using it.

Illustration of a charcoal document breaking out of a lime frame and a pink arrow pointing at a small terminal block

Impact

What was impacted
Ghostscript before 10.08.0. The bug is a use-after-free while the program loads fonts. A crafted document uses it to switch off the checks in -dSAFER, the sandbox that is supposed to stop a document from running commands or reaching files. Many applications never call Ghostscript by name. ImageMagick, Pillow, libvips, or a Qt plugin can hand it PostScript or EPS content even when the upload is named .png, .jpg, or .pdf. A thumbnail or a crop can start the interpreter. In the demonstrations the command ran as the low-privilege account that does the rendering.
Who was impacted
Linux servers that render uploads, previews, or print jobs with Ghostscript, including a separate copy inside a container or an application. Tests that needed no login included an anonymous print job on a shared Debian 13 queue, an email attachment that Roundcube processed when the recipient opened the message, and public upload forms in the WordPress plugins Forminator and Essential Addons for Elementor. WordPress Core needed an account that can upload files. Authors and higher roles have that by default. The CVE is classified as local, and those tests still reached Ghostscript from the network. As of the week before this November 22 report, a package survey listed Debian 12 (Bookworm) as vulnerable, fixes pending for Amazon Linux 2, Amazon Linux 2023, and Amazon Linux 2027 Preview, and fixes in progress for SUSE Linux Enterprise 12 SP5, parts of SUSE Linux Enterprise 15, and SUSE Linux Enterprise Server 16.0 and 16.1. The firm did not establish whether current Red Hat, Rocky Linux, AlmaLinux, Oracle Linux, or stable Fedora packages include the fix. That list is package status, not a tested attack path for each system.
What you need to do
Install Ghostscript 10.08.0, or a distribution package that contains that fix, on the copy the application actually runs. Updating the host package does not update a copy bundled in a container image or an application. WordPress closed its own upload path in 7.0.4 on August 12 under a different identifier, CVE-2026-65640. That fix and the Ghostscript fix cover different points in the same chain, so one does not replace the other. Until the renderer is updated, require a login on print queues and limit which file types the image processor accepts. In one test an AppArmor profile stopped the compromised interpreter from starting a shell. That is not a substitute for the update. Do not upload a crafted file to see if a server is exposed. Google fixed an affected path for this issue the week before this report. Similar problems reported at Dropbox and at other unnamed services are different Ghostscript bugs.

A crafted file can leave Ghostscript's sandbox and run commands on the server that processes it. The bug is CVE-2026-125396. Artifex fixed it in Ghostscript 10.08.0 on September 8 and is moving the vulnerable internal step into safer code. The developer who handled the fix described that step as old code, already known to be risky and hard to remove. The CVE was published the week before this report and is scored 8.5 out of 10 in the Ghostscript security advisory. Security firm pwn.ai says there have been no reports of the flaw being used in attacks. It showed that ordinary upload, preview, and print features in about ten common applications could be tricked into feeding Ghostscript the file.

An application does not have to call Ghostscript directly. ImageMagick, Pillow, libvips, or a Qt plugin will pass PostScript or EPS content to it, even when the file is named .png, .jpg, or .pdf. Making a thumbnail or cropping a picture can start the interpreter. The path depends on the libraries the application uses. The bug is a use-after-free in the font-loading code. A crafted document uses it to turn off -dSAFER. In the tests, the command ran each time as the low-privilege account that does the rendering.

Several paths needed no login. The demonstrations included an anonymous print job to a shared Debian 13 queue, an emailed attachment that Roundcube webmail processed the moment the recipient opened the message, and public upload forms in the WordPress plugins Forminator and Essential Addons for Elementor. WordPress Core needed an account allowed to upload files. Authors and higher roles have that ability by default. The CVE is classified as a local flaw. The tests still reached Ghostscript from the network through print jobs, email, and web uploads.

The Ghostscript package on the host is not the only copy that matters. A document worker can keep running an old build bundled in a container image or an application after the operating system package is replaced. WordPress had already closed its own upload path in version 7.0.4 on August 12, under CVE-2026-65640. Updating WordPress does not patch Ghostscript, and updating Ghostscript does not apply that WordPress fix. Distribution coverage was uneven as of the week before this report. The firm's list records package status, not a confirmed attack against each system. Debian 12 (Bookworm) was listed as vulnerable. Fixes were pending for Amazon Linux 2, Amazon Linux 2023, and Amazon Linux 2027 Preview. Fixes were in progress for SUSE Linux Enterprise 12 SP5, parts of SUSE Linux Enterprise 15, and SUSE Linux Enterprise Server 16.0 and 16.1. The firm did not establish whether current Red Hat, Rocky Linux, AlmaLinux, Oracle Linux, or stable Fedora packages carry the fix.

Until the renderer in use is on the fixed code, require authentication on print queues and limit which file types an image processor accepts. In one test an AppArmor profile stopped the compromised interpreter from starting a shell. Google fixed an affected path for this issue the week before this report. Reports of similar problems at Dropbox and at other services the firm did not name are separate Ghostscript bugs, not CVE-2026-125396. Do not send a crafted file to check whether a host is still exposed.

For your AI agent

Agent instructions — copy paste to Claude

You are helping me respond to CVE-2026-125396, a use-after-free in Ghostscript before version 10.08.0. A crafted file can turn off the -dSAFER sandbox and run commands as the account that renders the file. Do not write, upload, email, or print a crafted PostScript, EPS, PDF, or image file. Do not build a proof of concept or describe how to disable -dSAFER. Ask before installing a package, rebuilding an image, changing a print queue, editing an AppArmor profile, or changing who can upload files.

Facts from the report:
- Artifex fixed the flaw in Ghostscript 10.08.0 on September 8. The project is moving the vulnerable internal step into safer code. The developer who handled the fix described that step as old code that was already known to be risky and hard to remove. The CVE was published the week before this November 22 report and is scored 8.5 out of 10 in the Ghostscript security advisory. The report says there have been no attacks using it.
- The bug is a use-after-free while Ghostscript loads fonts. A crafted document can use it to switch off -dSAFER, which is supposed to stop the document from running commands or reaching files. Do not turn that description into a file.
- Applications often reach Ghostscript through ImageMagick, Pillow, libvips, or a Qt plugin, even when the upload is named .png, .jpg, or .pdf. A thumbnail or a crop can start the interpreter. The exact path depends on the libraries in use. Do not invent other library names.
- pwn.ai showed ordinary upload, preview, and print features in about ten common applications handing the file to Ghostscript. The command ran as the low-privilege account that does the rendering. Do not treat "low privilege" as harmless.
- Paths that needed no login in the tests: an anonymous print job on a shared Debian 13 queue, an attachment Roundcube processed when the recipient opened the message, and public upload forms in the WordPress plugins Forminator and Essential Addons for Elementor. WordPress Core needed an account that can upload. Authors and higher roles have that by default. The CVE is classified as local. The tests still reached Ghostscript from the network. The per-application versions and the access each one needed are in the firm's impact index, which this brief does not reproduce. If I do not show you a version, say it is unknown.
- A host operating-system update does not replace Ghostscript bundled in a container image or an application.
- WordPress closed its own upload path in 7.0.4 on August 12 under CVE-2026-65640. That fix and Ghostscript 10.08.0 cover different points in the same chain. Updating one does not remove the need for the other.
- Package survey as of the week before this report, status only, not a tested attack path: Debian 12 (Bookworm) listed as vulnerable. Fix pending on Amazon Linux 2, Amazon Linux 2023, and Amazon Linux 2027 Preview. Fix in progress on SUSE Linux Enterprise 12 SP5, parts of SUSE Linux Enterprise 15, and SUSE Linux Enterprise Server 16.0 and 16.1. The firm did not establish whether current Red Hat, Rocky Linux, AlmaLinux, Oracle Linux, or stable Fedora packages include the fix. Check the version on the system. Do not mark a distribution safe because it is missing from the vulnerable list.
- Until the renderer is updated, require authentication on print queues and limit which file types the image processor accepts. In one test an AppArmor profile stopped the compromised interpreter from starting a shell. That is one test, not a complete workaround.
- Google fixed an affected path for this issue the week before this report. Similar reports at Dropbox and at other unnamed services are different Ghostscript bugs. Do not close this CVE because a different Ghostscript issue was patched.

Context:
- What was impacted: Ghostscript before 10.08.0, including copies reached through image and document libraries and copies bundled in containers or applications.
- Who should care: operators of Linux servers that render uploads, previews, email attachments, or print jobs, and WordPress sites on versions before 7.0.4 that also use Ghostscript.
- What to do: install Ghostscript 10.08.0 or a package that contains it, on the copy that actually runs, and update WordPress to 7.0.4 or later for CVE-2026-65640. Require login on print queues and limit accepted file types until that renderer is updated.

Do this in order. Ask before installing, rebuilding, or changing access. Prefer read-only inventory first. Do not write or run an exploit or a proof of concept.

1. Inventory
   - Find Ghostscript copies: the host package, containers, and applications that ship their own binary. Record the version if you can read it without changing the system. 10.08.0 is the fixed release named in this report. A version below that is in the affected range. If you cannot read a version, say so. Do not mark an unknown version as safe.
   - Note ImageMagick, Pillow, libvips, and Qt plugins only when they are installed. Their presence means a render path may call Ghostscript. It does not by itself prove the app is one of the ten tested.
   - Record print queues that accept jobs without a login, Roundcube if it is in use, and WordPress including Forminator and Essential Addons for Elementor. For WordPress Core, record the version and whether Author or a higher role can upload. WordPress 7.0.4 is the release that closed CVE-2026-65640. Do not invent plugin version numbers. This report does not give them.
   - Record the distribution only as a clue. Confirm it with the package version on the machine.
2. Contain
   - If a renderer is still below 10.08.0, say so. Propose requiring authentication on print queues and limiting the file types the image processor accepts. Ask before changing either.
   - An AppArmor profile stopped a shell in one test. Do not enable or edit a profile unless I ask. Do not call it a fix.
3. Remediate
   - Plan Ghostscript 10.08.0, or the distribution package that contains that fix, for every copy you found, including images and bundled binaries. Ask before installing or rebuilding.
   - If WordPress is older than 7.0.4, plan that update for CVE-2026-65640 as well. Say that it does not replace the Ghostscript update.
   - Do not invent a workaround the report does not describe.
4. Verify
   - After an update I asked you to perform, read the Ghostscript version again, including inside any image I asked you to rebuild. Claim it is fixed only when that copy is 10.08.0 or I show you a package note that it contains this fix.
   - If WordPress was updated at my request, read that version again. 7.0.4 or later covers CVE-2026-65640 only.
   - If I did not ask you to change anything, report the inventory only.
5. Report back
   - Which Ghostscript copies you found, their versions, which ones a host package update would miss, the WordPress version if present, what you changed, and that the report has not described attacks using this flaw.

Do not invent CVEs, package versions, or a list of affected applications beyond the ones named here. If a check needs access I have not given you, say what you need and stop.

← All news

Try the platform.

Open the demo workspace with mock data. No login. Register from the banner when you want early access. No security team. No call.

Try the platform