Upload2Shell (CVE-2026-125396)

f311a 101 points 46 comments November 21, 2026
pwn.ai · View on Hacker News

Discussion Highlights (14 comments)

dabinat

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

baggy_trough

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

philipwhiuk

Weird title. Feels like it should be GhostScript2Shell. And the disclosure process is problematic if it's all the same issue.

derac

this name is god awful. ask an llm to name your thing or something

hannob

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.

dgacmu

Wish they'd named it Shell In The Ghost

layer8

I’m waiting for Stairway2Shell.

dvh

Do you think people will finally start removing decade old cruft from libraries and/or start creating single purpose minimal libraries? Or will the defense be just reactionary and on per cve basis?

freecodeio

this title isn't helping and is just clickbait

topranks

Seems like they did the right thing disclosure wise anyway. Who cares about the name all bugs get stupid names.

megous

ghostscript, imagemagick, ffmpeg, etc. etc. all these passthrough data in data out programs that don't need much of anything from the system, I'd think people would run them with untrusted input in a tight whitelist based seccomp+landlock sandbox. it's a bit annoying if they are not statically compiled, due to ld.so loading libraries, but possible.

int0x29

That timeline is unreadable. Just say what was found impacted when with versions along with patch dates and versions. I don't need to know about case studies that will hypothetically be written. I don't need little blurbs under everything. "What we said" should instead be "publicly disclosed." Honestly the whole thing should be a table so you can group the different bits of the timeline for different software/services by software/service rather than time.

varenc

I'm dubious of some of the claims in the timeline. I have no doubt they found an RCE vuln, but people know that your document rendering service should be sandboxed (beyond Ghostscript's sandbox). So it's a bit disingenuous not to acknowledge that their RCEs for companies like Google and Dropbox almost certainly only get them into tightly sandboxed servers that lacked any sensitive access, exactly for this reason.

rietta

ghostscript is everywhere. It's also AGPL, which I am not certain is commonly understood.

Semantic search powered by Rivestack pgvector
13,334 stories · 126,150 chunks indexed