It's been known for a while, and certainly long before the recent AI vuln flood, that ghostscript is really problematic in terms of security.
Ultimately, postscript is its own programming language, and executing a programming language in a secure, sandboxed way is not trivial. ghostscript has only a very poor pseudo sandbox that fails regularly. Unfortunately, ghostscript is the only implementation of postscript that's out there.
All of that would matter much less if people only used it to parse postscript. But it's used indirectly by imagemagick (you can disable it), which means many people using imagemagick to parse images from untrusted sources get exposed to ghostscript's poor security.
dabinat | 2 hours ago
TacticalCoder | an hour ago
https://security-tracker.debian.org/tracker/CVE-2026-125396
baggy_trough | an hour ago
philipwhiuk | an hour ago
And the disclosure process is problematic if it's all the same issue.
fock | an hour ago
derac | an hour ago
hannob | 53 minutes ago
Ultimately, postscript is its own programming language, and executing a programming language in a secure, sandboxed way is not trivial. ghostscript has only a very poor pseudo sandbox that fails regularly. Unfortunately, ghostscript is the only implementation of postscript that's out there.
All of that would matter much less if people only used it to parse postscript. But it's used indirectly by imagemagick (you can disable it), which means many people using imagemagick to parse images from untrusted sources get exposed to ghostscript's poor security.
dgacmu | 45 minutes ago
steve1977 | 25 minutes ago