p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in graphicsmagick

In den letzten 30 Tagen veröffentlichte Sicherheitslücke für graphicsmagick: 1. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 14

  1. CVE-2026-103118

    Mittel · CVSS 5.3EPSS 0,29%Keine Korrektur veröffentlicht

    GraphicsMagick WPG File wpg.c ExtractPostscript recursion

    A vulnerability was detected in GraphicsMagick up to 1.3.47. Affected by this vulnerability is the function ExtractPostscript of the file coders/wpg.c of the component WPG File Handler. Performing a manipulation results in uncontrolled recursion. The attack may be initiated remotely. The patch is named 627b5b1b2fc2. It is suggested to install a patch to address this issue. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

    Veröffentlicht Aktualisiert
  2. CVE-2026-77118

    Hoch · CVSS 8.4EPSS 0,17%Keine Korrektur veröffentlicht

    Out-of-bounds write in GraphicsMagick PCD decoder

    A heap out-of-bounds write exists in the Photo CD (PCD) decoder of GraphicsMagick. In DecodeImage() (coders/pcd.c), the Huffman delta loop advances its output pointer with q++ after every decoded delta and never checks it against the end of the heap-allocated luma/chroma plane buffers. The pointer is repositioned only when a sync marker introduces a new plane/row; between sync markers the run length is bounded solely by the input. A crafted PCD file that positions the pointer near the end of a plane and then supplies a long run of deltas with no intervening sync therefore walks the pointer past the end of the allocation and writes through

    Veröffentlicht Aktualisiert
  3. CVE-2025-12474

    Niedrig · CVSS 2.3EPSS 0,11%Keine Korrektur veröffentlicht

    libjxl: Uninitialized memory read in decoder due to incorrect optimization in patch handling

    A specially-crafted file can cause libjxl's decoder to read pixel data from uninitialized (but allocated) memory. This can be done by causing the decoder to reference an outside-image-bound area in a subsequent patches. An incorrect optimization causes the decoder to omit populating those areas.

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →