Upload2Shell · CVE-2026-125396

36 points by f311a 2 hours ago on hackernews | 9 comments

dabinat | 2 hours ago

This seems like important information but this page is completely unreadable.

TacticalCoder | an hour ago

baggy_trough | an hour ago

If you want to use Ghostscript in a secure manner, you're going to have a bad time.

philipwhiuk | an hour ago

Weird title. Feels like it should be GhostScript2Shell.

And the disclosure process is problematic if it's all the same issue.

probably also the thumbnailer in your favourite linux-desktop. And the file-indexer ...

derac | an hour ago

this name is god awful. ask an llm to name your thing or something
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.

Wish they'd named it Shell In The Ghost

steve1977 | 25 minutes ago

We don't do human creativity around here sir.