Gdk-Pixbuf
GNOME- Product type
- Other
- Catalog vulnerabilities
- 21
Severity across 3 analyzed records
en
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScanVerify to analyze this security profile
As of 09/13/2026, within CyStack's analyzed data, Gdk-Pixbuf has 1 security vulnerability published in the last 90 days. Of these, 0 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of Gdk-Pixbuf and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-16768Gdk-pixbuf: out-of-bounds read in ico parser | Exploitation statusPublic exploit | FixNot confirmed | Published07/23/2026 | SeverityMedium |
CVE-2026-5201Gdk-pixbuf: gdk-pixbuf: denial of service via heap-based buffer overflow when processing a specially crafted jpeg image | Exploitation statusNot known exploited | FixNot confirmed | Published03/31/2026 | SeverityHigh |
CVE-2021-46829 | Exploitation statusNot confirmed | FixNot confirmed | Published07/24/2022 | SeverityUnknown |
CVE-2021-20240 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2021 | SeverityUnknown |
CVE-2020-29385 | Exploitation statusNot confirmed | FixNot confirmed | Published12/26/2020 | SeverityUnknown |
CVE-2011-2897 | Exploitation statusNot confirmed | FixNot confirmed | Published11/12/2019 | SeverityUnknown |
CVE-2017-12447 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2019 | SeverityUnknown |
CVE-2017-1000422 | Exploitation statusNot confirmed | FixNot confirmed | Published01/02/2018 | SeverityUnknown |
CVE-2017-2862 | Exploitation statusNot confirmed | FixNot confirmed | Published09/05/2017 | SeverityHigh |
CVE-2017-2870 | Exploitation statusNot confirmed | FixNot confirmed | Published09/05/2017 | SeverityHigh |
CVE-2017-6313 | Exploitation statusNot confirmed | FixNot confirmed | Published03/10/2017 | SeverityUnknown |
CVE-2017-6312 | Exploitation statusNot confirmed | FixNot confirmed | Published03/10/2017 | SeverityUnknown |
CVE-2017-6311 | Exploitation statusNot confirmed | FixNot confirmed | Published03/10/2017 | SeverityUnknown |
CVE-2017-6314 | Exploitation statusNot confirmed | FixNot confirmed | Published03/10/2017 | SeverityUnknown |
CVE-2016-6352 | Exploitation statusNot confirmed | FixNot confirmed | Published10/03/2016 | SeverityUnknown |
CVE-2015-8875 | Exploitation statusNot confirmed | FixNot confirmed | Published06/01/2016 | SeverityUnknown |
CVE-2015-7674 | Exploitation statusNot confirmed | FixNot confirmed | Published10/26/2015 | SeverityUnknown |
CVE-2015-7673 | Exploitation statusNot confirmed | FixNot confirmed | Published10/26/2015 | SeverityUnknown |
CVE-2015-4491 | Exploitation statusNot confirmed | FixNot confirmed | Published08/16/2015 | SeverityUnknown |
CVE-2012-2370 | Exploitation statusNot confirmed | FixNot confirmed | Published08/13/2012 | SeverityUnknown |
CVE-2011-2485 | Exploitation statusNot confirmed | FixNot confirmed | Published07/03/2012 | SeverityUnknown |