CVE-2026-81893

MEDIUMPre-NVD 4.74.7
EchelonGraph scoreMEDIUM confidence

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

Score 4.7 from GitHub Security Advisory published 2026-08-27. A secondary CVSS source baseline 4.7; 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
4.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in gdk-pixbuf. When loading a specially crafted JPEG image containing chunked ICC profile markers, an error during ICC profile parsing can leave stale size metadata after the profile buffer is freed. A subsequent allocation in the same decode can cause an out-of-bounds write, potentially crashing the application. To exploit this flaw, an application using gdk-pixbuf must process the malicious JPEG image.

Affected version >= 2.26.4

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity47% × 45%
The EG Score, 4.7 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.2%
EPSS %ILE
3rd
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 27, 2026

Last Modified

August 28, 2026

Advisory Details (4)

Auto-updated Aug 27, 2026
Patch available. Sources: redhat.
Web page

jpeg: When freeing memory, unset the size (!278) · Merge requests · GNOME / gdk-pixbuf · GitLab

https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/278
Red Hat

2524834 – (CVE-2026-81893) CVE-2026-81893 gdk-pixbuf: gdk-pixbuf: invalid write in JPEG ICC profile parser on error recovery

https://bugzilla.redhat.com/show_bug.cgi?id=2524834
Red HatMentions a patch (unverified)

CVE-2026-81893 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-81893

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
gdk-pixbuf2.42.10+dfsg-1 ... 2.44.8+dfsg-1 (26 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
gdk-pixbuf2.42.12+dfsg-4 ... 2.44.8+dfsg-1 (17 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
gdk-pixbuf2.42.12+dfsg-4 ... 2.44.7+dfsg-1 (15 versions)
  • every version up to 2.44.8+dfsg-1: fixed in 2.44.8+dfsg-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 98× 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 99 of 152 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 53 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.2% · 3rd percentile
  2. 2026-10-12 14:56 UTCEG score recompute
  3. 2026-10-11 19:20 UTCEG score recompute
  4. 2026-10-11 16:36 UTCEG score recompute
  5. 2026-10-11 13:54 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  8. 2026-10-10 01:46 UTCEG score recompute
  9. 2026-10-10 01:46 UTCVendor advisory
  10. 2026-10-10 01:46 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  12. 2026-10-09 02:56 UTCEG score recompute
  13. 2026-10-09 02:56 UTCVendor advisory
  14. 2026-10-09 02:56 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  15. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  16. 2026-10-08 01:14 UTCEG score recompute
  17. 2026-10-08 01:14 UTCVendor advisory
  18. 2026-10-08 01:14 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  20. 2026-10-06 15:56 UTCEG score recompute
  21. 2026-10-06 15:56 UTCVendor advisory
  22. 2026-10-06 15:56 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  24. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  25. 2026-10-05 16:51 UTCEG score recompute
Show 74 more
  1. 2026-10-05 16:51 UTCVendor advisory
  2. 2026-10-05 16:51 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  3. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  4. 2026-10-04 16:29 UTCVendor advisory
  5. 2026-10-04 16:29 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  6. 2026-10-03 17:39 UTCEG score recompute
  7. 2026-10-03 17:39 UTCVendor advisory
  8. 2026-10-03 17:39 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  9. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  10. 2026-10-02 18:50 UTCEG score recompute
  11. 2026-10-02 18:50 UTCVendor advisory
  12. 2026-10-02 18:50 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  13. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  14. 2026-10-01 19:52 UTCEG score recompute
  15. 2026-10-01 19:52 UTCVendor advisory
  16. 2026-10-01 19:52 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  18. 2026-09-30 19:54 UTCEG score recompute
  19. 2026-09-30 19:54 UTCVendor advisory
  20. 2026-09-30 19:54 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  21. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  22. 2026-09-29 15:14 UTCEG score recompute
  23. 2026-09-29 15:14 UTCVendor advisory
  24. 2026-09-29 15:14 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  25. 2026-09-28 16:24 UTCEG score recompute
  26. 2026-09-28 16:24 UTCVendor advisory
  27. 2026-09-28 16:24 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  28. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  29. 2026-09-27 17:15 UTCEG score recompute
  30. 2026-09-27 17:15 UTCVendor advisory
  31. 2026-09-27 17:15 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  33. 2026-09-26 18:24 UTCEG score recompute
  34. 2026-09-26 18:24 UTCVendor advisory
  35. 2026-09-26 18:24 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  36. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  37. 2026-09-25 15:45 UTCVendor advisory
  38. 2026-09-25 15:45 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  39. 2026-09-24 16:47 UTCEG score recompute
  40. 2026-09-24 16:47 UTCVendor advisory
  41. 2026-09-24 16:47 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  42. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  43. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  44. 2026-09-23 17:41 UTCVendor advisory
  45. 2026-09-23 17:41 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  46. 2026-09-22 18:23 UTCEG score recompute
  47. 2026-09-22 18:23 UTCVendor advisory
  48. 2026-09-22 18:22 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  49. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  50. 2026-09-21 17:59 UTCVendor advisory
  51. 2026-09-21 17:59 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  52. 2026-09-20 19:09 UTCVendor advisory
  53. 2026-09-20 19:09 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  54. 2026-09-19 20:19 UTCVendor advisory
  55. 2026-09-19 20:19 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  56. 2026-09-18 21:29 UTCEG score recompute
  57. 2026-09-18 21:29 UTCVendor advisory
  58. 2026-09-18 21:29 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  59. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  60. 2026-09-17 21:28 UTCEG score recompute
  61. 2026-09-17 21:28 UTCVendor advisory
  62. 2026-09-17 21:28 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  63. 2026-09-16 22:38 UTCEG score recompute
  64. 2026-09-16 22:38 UTCVendor advisory
  65. 2026-09-16 22:38 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  66. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  67. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  68. 2026-09-15 23:30 UTCEG score recompute
  69. 2026-09-15 23:30 UTCVendor advisory
  70. 2026-09-15 23:30 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  71. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  72. 2026-09-15 00:04 UTCVendor advisory
  73. 2026-09-15 00:04 UTCGHSA enrichmentGHSA-237w-6c39-25rh · GitHub CVSS 4.7
  74. 2026-09-14 01:13 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-81893?
CVE-2026-81893 is a medium-severity vulnerability; its CVE record was published on August 27, 2026. A flaw was found in gdk-pixbuf. When loading a specially crafted JPEG image containing chunked ICC profile markers, an error during ICC profile parsing can leave stale size metadata after the profile buffer is freed. A subsequent allocation in the same decode can cause an out-of-bounds write,…
When was CVE-2026-81893 made public?
CVE-2026-81893 was made public on August 27, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-81893 actively exploited?
CVE-2026-81893 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81893?
CVE-2026-81893 has a CVSS base score of 4.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81893?
A fix for CVE-2026-81893 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-81893 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-81893

Explore →

Is Your Infrastructure Affected by CVE-2026-81893?

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