CVE-2026-77118

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (6th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-63345 (ENISA EUVD) · GHSA-qjrj-qxx7-fc4j (GitHub Security Advisories)Source: ENISA EUVD

8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Seal Security) states them: "Upgrade to GraphicsMagick 1.3.48 or later, which bounds the decode output pointer against the end of each plane buffer and over-provisions the buffers."

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 it. Processing an untrusted PCD file — for example with gm convert or gm identify, or through any application linked against libGraphicsMagick — can corrupt heap memory beyond the buffers.

CVSS
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 20, 2026

Last Modified

October 27, 2026

Advisory Details (2)

Auto-updated Aug 20, 2026
Patch available.
Web page

coders/pcd.c (ReadPCDImage): Over-provision the per-channel Huffman decode... (937cdd9920bd) · Commits · GraphicsMagick / graphicsmagick · GitLab

https://foss.heptapod.net/graphicsmagick/graphicsmagick/-/commit/937cdd9920bd96

Vendor Advisories for CVE-2026-77118(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
graphicsmagick1.4+really1.3.40-4 ... 1.4+really1.3.49-1 (17 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
graphicsmagick1.4+really1.3.45+hg17696-1 ... 1.4+really1.3.49-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
graphicsmagick1.4+really1.3.45+hg17696-1, 1.4+really1.3.46-1, 1.4+really1.3.46-2
  • every version up to 1.4+really1.3.48-1: fixed in 1.4+really1.3.48-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 249 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 149 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-11-17 17:51 UTCEchelonGraph re-scored
  6. 2026-11-17 17:51 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  7. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-11-16 16:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-11-15 17:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-11-14 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-11-10 18:48 UTCEchelonGraph re-scored
  15. 2026-11-10 18:48 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  16. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-11-03 20:43 UTCEchelonGraph re-scored
  24. 2026-11-03 20:43 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  25. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 75 more
  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-10-27 21:09 UTCEchelonGraph re-scored
  8. 2026-10-27 21:09 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-27 10:26 UTCEchelonGraph re-scored
  11. 2026-10-27 10:26 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  12. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-25 14:01 UTCEchelonGraph re-scored
  15. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-20 08:14 UTCEchelonGraph re-scored
  21. 2026-10-20 08:14 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  22. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-10-18 03:12 UTCEchelonGraph re-scored
  25. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  26. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-10-13 07:00 UTCEchelonGraph re-scored
  31. 2026-10-13 07:00 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  32. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  33. 2026-10-12 15:37 UTCEchelonGraph re-scored
  34. 2026-10-11 19:23 UTCEchelonGraph re-scored
  35. 2026-10-11 16:39 UTCEchelonGraph re-scored
  36. 2026-10-11 13:58 UTCEchelonGraph re-scored
  37. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  38. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  39. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  40. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-10-08 05:31 UTCEchelonGraph re-scored
  42. 2026-10-08 05:31 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  43. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  44. 2026-10-07 03:49 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  45. 2026-10-06 16:54 UTCEchelonGraph re-scored
  46. 2026-10-06 16:54 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  47. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-10-06 03:31 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  49. 2026-10-06 03:30 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  50. 2026-10-06 03:29 UTCEchelonGraph re-scored
  51. 2026-10-06 03:29 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  52. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-10-05 13:52 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  54. 2026-10-05 02:34 UTCEchelonGraph re-scored
  55. 2026-10-05 02:34 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  56. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  57. 2026-10-04 15:41 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  58. 2026-10-04 04:24 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  59. 2026-10-03 17:31 UTCEchelonGraph re-scored
  60. 2026-10-03 17:31 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  61. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  62. 2026-10-03 06:38 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  63. 2026-10-02 19:18 UTCEchelonGraph re-scored
  64. 2026-10-02 19:18 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  65. 2026-10-02 08:24 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  66. 2026-10-01 21:31 UTCEchelonGraph re-scored
  67. 2026-10-01 21:31 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  68. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  69. 2026-10-01 07:25 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  70. 2026-09-30 20:32 UTCEchelonGraph re-scored
  71. 2026-09-30 20:32 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  72. 2026-09-30 08:21 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  73. 2026-09-29 01:58 UTCEchelonGraph re-scored
  74. 2026-09-29 01:58 UTCGHSA enrichmentGHSA-qjrj-qxx7-fc4j · GitHub severity HIGH
  75. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 5th percentile

Frequently asked(5)

What is CVE-2026-77118?
CVE-2026-77118 is a high-severity vulnerability; its CVE record was published on August 20, 2026. 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…
When was CVE-2026-77118 made public?
CVE-2026-77118 was made public on August 20, 2026: that is the date its CVE record's CNA, Seal Security, gives for when the vulnerability was made public. The CVE record itself was published on August 20, 2026. EchelonGraph's copy of the record carries a last-modified date of October 27, 2026; the record at its source may have been updated since.
Is CVE-2026-77118 actively exploited?
CVE-2026-77118 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77118?
CVE-2026-77118 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77118?
A fix for CVE-2026-77118 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Seal Security) states them: "Upgrade to GraphicsMagick 1.3.48 or later, which bounds the decode output pointer against the end of each plane buffer and over-provisions the buffers." The vendor advisories EchelonGraph has for CVE-2026-77118 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-77118

Explore →

Is Your Infrastructure Affected by CVE-2026-77118?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.