CVE-2026-77118
Heap out-of-bounds write in GraphicsMagick PCD decoder leads to heap corruption.
Is CVE-2026-77118 being exploited?
Not confirmed. CVE-2026-77118 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.
How severe is CVE-2026-77118?
CVE-2026-77118 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-77118?
Yes. A fix has been recorded for CVE-2026-77118. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-77118 affect?
CVE-2026-77118 affects GraphicsMagick (libGraphicsMagick), gm convert, gm identify, Any application linking libGraphicsMagick. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-77118?
Block/unpack untrusted PCD files; disable PCD coder or apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted PCD files can trigger heap OOB writes during decoding, causing crashes, memory corruption and potential remote code execution in processes using libGraphicsMagick.
Patch when possible
- affected< 1.4+really1.3.48-1
- affected>= 1.0.0 and < 1.3.48
- affected< 1.3.48
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.