Upload2Shell · CVE-2026-125396

(pwn.ai)

26 points | by f311a 2 hours ago

8 comments

  • hannob 18 minutes ago
    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
    This seems like important information but this page is completely unreadable.
  • Insimwytim 12 minutes ago
    At the time of heartbleed and the likes, we may have not had the best code, but at least people who named things were a little bit more imaginative.
  • dgacmu 11 minutes ago
    Wish they'd named it Shell In The Ghost
  • derac 31 minutes ago
    this name is god awful. ask an llm to name your thing or something
  • philipwhiuk 42 minutes ago
    Weird title. Feels like it should be GhostScript2Shell.

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

    • fock 26 minutes ago
      probably also the thumbnailer in your favourite linux-desktop. And the file-indexer ...
  • baggy_trough 1 hour ago
    If you want to use Ghostscript in a secure manner, you're going to have a bad time.