CVE-2025-7345

A flaw exists in gdk‑pixbuf within the gdk_pixbuf__jpeg_image_load_increment function (io-jpeg.c) and in glib’s g_base64_encode_step (glib/gbase64.c). When processing maliciously crafted JPEG images, a heap buffer overflow can occur during Base64 encoding, allowing out-of-bounds reads from heap memory, potentially causing application crashes or arbitrary code execution.

gdk is written in C but has been designed from the ground up to support a wide range of languages. It provide a complete set of widgets,and suitable for projects ranging from small one-off tools to complete application suites.

Security Fix(es):

A vulnerability was found in gdk‑pixbuf (affected version not known). It has been rated as critical.Using CWE to declare the problem leads to CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().Impacted is confidentiality, integrity, and availability.There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.(CVE-2025-7345)

The gdk-pixbuf2 packages provide an image loading library that can be extended by loadable modules for new image formats. It is used by toolkits such as GTK+ or clutter.

Security Fix(es):

• gdk?pixbuf: Heap?buffer?overflow in gdk?pixbuf (CVE-2025-7345)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The gdk-pixbuf2 packages provide an image loading library that can be extended by loadable modules for new image formats. It is used by toolkits such as GTK+ or clutter.

Security Fix(es):

• gdk?pixbuf: Heap?buffer?overflow in gdk?pixbuf (CVE-2025-7345)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The gdk-pixbuf2 packages provide an image loading library that can be extended by loadable modules for new image formats. It is used by toolkits such as GTK+ or clutter.

Security Fix(es):

• gdk?pixbuf: Heap?buffer?overflow in gdk?pixbuf (CVE-2025-7345)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

A flaw exists in gdk‑pixbuf within the gdk_pixbuf__jpeg_image_load_increment function (io-jpeg.c) and in glib’s g_base64_encode_step (glib/gbase64.c). When processing maliciously crafted JPEG images, a heap buffer overflow can occur during Base64 encoding, allowing out-of-bounds reads from heap memory, potentially causing application crashes or arbitrary code execution.

The gdk-pixbuf2 packages provide an image loading library that can be extended by loadable modules for new image formats. It is used by toolkits such as GTK+ or clutter.

Security Fix(es):

• gdk?pixbuf: Heap?buffer?overflow in gdk?pixbuf (CVE-2025-7345)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

A flaw exists in gdk‑pixbuf within the gdk_pixbuf__jpeg_image_load_increment function (io-jpeg.c) and in glib’s g_base64_encode_step (glib/gbase64.c). When processing maliciously crafted JPEG images, a heap buffer overflow can occur during Base64 encoding, allowing out-of-bounds reads from heap memory, potentially causing application crashes or arbitrary code execution.

A flaw exists in gdk‑pixbuf within the gdk_pixbuf__jpeg_image_load_increment function (io-jpeg.c) and in glib’s g_base64_encode_step (glib/gbase64.c). When processing maliciously crafted JPEG images, a heap buffer overflow can occur during Base64 encoding, allowing out-of-bounds reads from heap memory, potentially causing application crashes or arbitrary code execution.

• CVE-2025-7345: fix heap buffer overflow during base64 encoding in gdk_pixbuf__jpeg_image_load_increment()

• CVE-2025-7345: fix heap buffer overflow during base64 encoding in gdk_pixbuf__jpeg_image_load_increment()

• CVE-2025-7345: fix heap buffer overflow during base64 encoding in gdk_pixbuf__jpeg_image_load_increment()

• CVE-2025-7345: fix heap buffer overflow during base64 encoding in gdk_pixbuf__jpeg_image_load_increment()

Heap‑buffer‑overflow in gdk‑pixbuf. (CVE-2025-7345) Out-of-bounds read in ico parser. (CVE-2026-16768) Invalid write in jpeg icc profile parser on error recovery. (CVE-2026-81893)

These are all security issues fixed in the gdk-pixbuf-devel-2.42.12-5.1 package on the GA media of openSUSE Tumbleweed.

This update for gdk-pixbuf fixes the following issues:

• CVE-2025-7345: heap buffer overflow in gdk-pixbuf within the gdk_pixbuf__jpeg_image_load_increment function (io-jpeg.c) and in glib g_base64_encode_step (bsc#1246114).
• CVE-2025-6199: uninitialized memory could lead to leak arbitrary memory contents (bsc#1245227).

Root has patched CVE-2025-7345 in the rootio-gdk-pixbuf package for Root:Debian:12. Multiple fixed versions available.

This update for gdk-pixbuf fixes the following issues:

• CVE-2025-6199: Fixed uninitialized memory leading to arbitrary memory contents leak (bsc#1245227)
• CVE-2025-7345: Fixed heap buffer overflow within the gdk_pixbuf__jpeg_image_load_increment function (bsc#1246114)

This update for gdk-pixbuf fixes the following issues:

• CVE-2025-6199: Fixed uninitialized memory leading to arbitrary memory contents leak (bsc#1245227)
• CVE-2025-7345: Fixed heap buffer overflow within the gdk_pixbuf__jpeg_image_load_increment function (bsc#1246114)

This update for gdk-pixbuf fixes the following issues:

• CVE-2025-7345: Fixed heap buffer overflow in gdk_pixbuf__jpeg_image_load_increment function (bsc#1246114)

This update for gdk-pixbuf fixes the following issues:

• CVE-2025-7345: heap buffer overflow in gdk‑pixbuf within the gdk_pixbuf__jpeg_image_load_increment function (bsc#1246114).
• CVE-2025-6199: uninitialized memory could lead to leak arbitrary memory contents (bsc#1245227).

This update for gdk-pixbuf fixes the following issues:

• CVE-2025-7345: Uninitialized memory could lead to leak arbitrary memory contents (bsc#1246114).
• CVE-2025-6199: Heap buffer overflow within the gdk_pixbuf__jpeg_image_load_increment function (bsc#1245227).

This update for gdk-pixbuf fixes the following issues:

• CVE-2025-6199: Fixed uninitialized memory leading to arbitrary memory leak (bsc#1245227)
• CVE-2025-7345: Fixed heap buffer overflow within the gdk_pixbuf__jpeg_image_load_increment function (bsc#1246114)

This update for gdk-pixbuf fixes the following issues:

• CVE-2025-7345: heap buffer overflow in gdk-pixbuf within the gdk_pixbuf__jpeg_image_load_increment function (io-jpeg.c) and in glib g_base64_encode_step (bsc#1246114).
• CVE-2025-6199: uninitialized memory could lead to leak arbitrary memory contents (bsc#1245227).

This update for gdk-pixbuf fixes the following issues:

• CVE-2025-7345: heap buffer overflow in gdk-pixbuf within the gdk_pixbuf__jpeg_image_load_increment function (io-jpeg.c) and in glib g_base64_encode_step (bsc#1246114).
• CVE-2025-6199: uninitialized memory could lead to leak arbitrary memory contents (bsc#1245227).

It was discovered that GDK-Pixbuf incorrectly handled certain GIF files. An attacker could possibly use this issue to expose sensitive information. This issue only affected Ubuntu 25.04, Ubuntu 24.04 LTS, Ubuntu 22.04 LTS, and Ubuntu 20.04 LTS. (CVE-2025-6199)

It was discovered that GDK-Pixbuf incorrectly handled certain JPEG files. An attacker could possibly use this issue to cause a crash or execute arbitrary code. (CVE-2025-7345)