CVE-2026-77219

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Score 7.1 from GitHub Security Advisory published 2026-08-21. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.1EG
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.1%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GNU Emacs before 31.0.91 contains an integer overflow in the PBM/PPM/PGM image loader that allows an attacker to leak heap memory contents by supplying a crafted image with large dimensions and an elevated max color index. The image loader multiplies image dimensions and channel count using signed integer arithmetic; for sufficiently large values, the result wraps to a negative number, bypassing the bounds check and causing the pixel reader to access heap memory past the end of the allocated buffer. The over-read contents are interpreted as pixel color values and rendered on screen.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.1% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.1%
EPSS %ILE
2nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 21, 2026

Last Modified

October 12, 2026

Advisory Details (2)

Auto-updated Aug 21, 2026
Patch available. Sources: github_commit.
Web page

GNU Emacs < 31.0.91 Heap Over-Read via PBM/PPM/PGM Image Loader | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gnu-emacs-heap-over-read-via-pbm-ppm-pgm-image-loader
GitHub commit

commit b07e634e4cf4 (emacs-mirror/emacs)

Fix landed in emacs-mirror/emacs commit b07e634e4cf4 — awaiting tagged release

https://github.com/emacs-mirror/emacs/commit/b07e634e4cf45162ae0178e32092b040587f2c6c

Vendor Advisories for CVE-2026-77219(3)

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
emacs1:28.2+1-15 ... 1:30.2+1-9 (53 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
emacs1:30.1+1-6 ... 1:30.2+1-9 (16 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
emacs1:30.1+1-6 ... 1:30.2+1-9 (15 versions)
  • every version on: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 148× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 100 of 246 refreshes 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 146 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-77219?
CVE-2026-77219 is a high-severity vulnerability; its CVE record was published on August 21, 2026. GNU Emacs before 31.0.91 contains an integer overflow in the PBM/PPM/PGM image loader that allows an attacker to leak heap memory contents by supplying a crafted image with large dimensions and an elevated max color index. The image loader multiplies image dimensions and channel count using signed…
When was CVE-2026-77219 made public?
CVE-2026-77219 was made public on July 1, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 21, 2026. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-77219 actively exploited?
CVE-2026-77219 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77219?
CVE-2026-77219 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77219?
A fix for CVE-2026-77219 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-77219 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-77219

Explore →

Is Your Infrastructure Affected by CVE-2026-77219?

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

Book a Demo →Browse All CVEs