8 comments

  • hannob35 minutes ago
    It&#x27;s been known for a while, and certainly long before the recent AI vuln flood, that ghostscript is really problematic in terms of security.<p>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&#x27;s out there.<p>All of that would matter much less if people only used it to parse postscript. But it&#x27;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&#x27;s poor security.
  • dabinat2 hours ago
    This seems like important information but this page is completely unreadable.
    • TacticalCoder54 minutes ago
      For those on Debian, the usual:<p><a href="https:&#x2F;&#x2F;security-tracker.debian.org&#x2F;tracker&#x2F;CVE-2026-125396" rel="nofollow">https:&#x2F;&#x2F;security-tracker.debian.org&#x2F;tracker&#x2F;CVE-2026-125396</a>
  • dgacmu27 minutes ago
    Wish they&#x27;d named it Shell In The Ghost
    • steve19777 minutes ago
      We don&#x27;t do human creativity around here sir.
  • Insimwytim29 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.
  • derac47 minutes ago
    this name is god awful. ask an llm to name your thing or something
  • philipwhiuk58 minutes ago
    Weird title. Feels like it should be GhostScript2Shell.<p>And the disclosure process is problematic if it&#x27;s all the same issue.
    • fock42 minutes ago
      probably also the thumbnailer in your favourite linux-desktop. And the file-indexer ...
  • baggy_trough1 hour ago
    If you want to use Ghostscript in a secure manner, you&#x27;re going to have a bad time.