# CVE-2025-7345: Gdk‑pixbuf: heap‑buffer‑overflow in gdk‑pixbuf > Heap buffer overflow in gdk-pixbuf allows attackers to execute arbitrary code or crash applications via malicious JPEG images. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 8 Jul 2025 - **Updated:** 30 Jun 2026 - **Also known as:** ALSA-2025:13315, AZL-65034, AZL-65048, BELL-CVE-2025-7345, CLSA-2025-1757662747, CLSA-2025-1757698525, CLSA-2025-1758896091, CLSA-2025-1763371545, DEBIAN-CVE-2025-7345, DLA-4344-1, GHSA-xrq2-m5w8-p5wg, OESA-2025-1913, RHSA-2025:12841, RHSA-2025:12862, RHSA-2025:13315, RHSA-2025:14574, RHSA-2025:14575, RHSA-2025:14576, RHSA-2025:14585, RHSA-2025:14618, RHSA-2025:14646, RHSA-2025:14647, RHSA-2025:14683, RLSA-2025:12841, RLSA-2025:12862, RLSA-2025:13315, SUSE-SU-2025:03010-1, UBUNTU-CVE-2025-7345, openSUSE-SU-2025:15468-1 ## What is CVE-2025-7345? CVE-2025-7345 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2025-7345? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gdk-pixbuf2` | AlmaLinux:8 | All versions | 2.36.12-7.el8_10 | | `gdk-pixbuf2-devel` | AlmaLinux:8 | All versions | 2.36.12-7.el8_10 | | `gdk-pixbuf2-modules` | AlmaLinux:8 | All versions | 2.36.12-7.el8_10 | | `gdk-pixbuf2-xlib` | AlmaLinux:8 | All versions | 2.36.12-7.el8_10 | | `gdk-pixbuf2-xlib-devel` | AlmaLinux:8 | All versions | 2.36.12-7.el8_10 | | `gdk-pixbuf2` | Red Hat:enterprise_linux:10.0 | All versions | 0:2.42.12-4.el10_0 | | `gdk-pixbuf2-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:2.42.12-4.el10_0 | | `gdk-pixbuf2-debugsource` | Red Hat:enterprise_linux:10.0 | All versions | 0:2.42.12-4.el10_0 | | `gdk-pixbuf2-devel` | Red Hat:enterprise_linux:10.0 | All versions | 0:2.42.12-4.el10_0 | | `gdk-pixbuf2-devel-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:2.42.12-4.el10_0 | | `gdk-pixbuf2-modules` | Red Hat:enterprise_linux:10.0 | All versions | 0:2.42.12-4.el10_0 | | `gdk-pixbuf2-modules-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:2.42.12-4.el10_0 | | `gdk-pixbuf2-tests-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:2.42.12-4.el10_0 | | `gdk-pixbuf2-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-devel-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-modules` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-modules-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-tests-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-xlib-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-devel-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-modules-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-tests-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-xlib-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-devel-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-modules-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-tests-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-xlib` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-xlib-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2-xlib-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-7.el8_10 | | `gdk-pixbuf2` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.42.6-6.el9_6 | | `gdk-pixbuf2-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.42.6-6.el9_6 | | `gdk-pixbuf2-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.42.6-6.el9_6 | | `gdk-pixbuf2-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.42.6-6.el9_6 | ## How do I fix CVE-2025-7345? Apply the vendor's patch. ## Is CVE-2025-7345 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7345 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-7345 and fix it if it is affected. What it is: CVE-2025-7345 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7345 exists. Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-7345/ (Markdown: https://insights.sbomify.com/CVE-2025-7345/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7345 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7345 - OSV: https://osv.dev/vulnerability/CVE-2025-7345 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-7345/ Summaries are generated and may contain mistakes; the official description above is the record.