CVE-2026-16768

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory published 2026-07-23. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A flaw was found in gdk-pixbuf. When parsing a specially crafted ICO file with pixel values that exceed the defined palette range, an out-of-bounds read can occur due to improper bounds checking against the actual palette size. This vulnerability causes heap bytes to be interpreted as valid palette indices and rendered as RGB pixel values in the output image, allowing an attacker to extract heap content via the generated output, such as a thumbnail.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

July 23, 2026

Last Modified

July 31, 2026

Advisory Details (3)

Auto-updated Jul 26, 2026
Patch available. Sources: redhat.
Web page

(CVE-2026-16768) Out of bounds read in ICO parser (#302) · Issues · GNOME / gdk-pixbuf · GitLab

https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/302
Red Hat

2506437 – (CVE-2026-16768) CVE-2026-16768 gdk-pixbuf: out-of-bounds read in ICO parser

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

cve-details

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

Vendor Advisories for CVE-2026-16768(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
gdk-pixbuf2.42.10+dfsg-1 ... 2.44.7+dfsg-1 (32 versions)
  • every version on: no fix on record
—
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.8+dfsg-1 (16 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 54× 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 191 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 91 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-16768?
CVE-2026-16768 is a medium-severity vulnerability; its CVE record was published on July 23, 2026. A flaw was found in gdk-pixbuf. When parsing a specially crafted ICO file with pixel values that exceed the defined palette range, an out-of-bounds read can occur due to improper bounds checking against the actual palette size. This vulnerability causes heap bytes to be interpreted as valid palette…
When was CVE-2026-16768 made public?
CVE-2026-16768 was made public on June 8, 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 July 23, 2026. EchelonGraph's copy of the record carries a last-modified date of July 31, 2026; the record at its source may have been updated since.
Is CVE-2026-16768 actively exploited?
CVE-2026-16768 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16768?
CVE-2026-16768 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16768?
A fix for CVE-2026-16768 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-16768 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-16768

Explore →

Is Your Infrastructure Affected by CVE-2026-16768?

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

Book a Demo →Browse All CVEs