CVE-2025-7345 | Gdk‑pixbuf: heap‑buffer‑overflow in gdk‑pixbuf

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.

Published: 2025-07-08 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-7345 is rated Moderate Risk (57.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.94%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-7345

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-04 0.45% 0.94% +0.49%
2 2026-04-24 0.38% 0.45% +0.08%
3 2026-03-24 — 0.38% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-7345

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-7345

OS Trackers for CVE-2025-7345

vendor priority summary link
debian not yet assigned CVE-2025-7345 not yet assigned priority: Debian including 1 source packages (gdk-pixbuf), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-7345
redhat medium — https://access.redhat.com/security/cve/CVE-2025-7345
suse high CVE-2025-7345 severity important: SUSE including 354 source package names (2.2.1-5.5:gpg2-2.4.4-slfo.1.1_5.1, 2.2.1-7.2:gpg2-2.4.4-slfo.1.1_5.1, …), 1441 product×package rows across 219 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (219 product lines)): Known Not Affected 630, Fixed 573, Known Affected 231, First Fixed 7. https://www.suse.com/security/cve/CVE-2025-7345/
ubuntu medium CVE-2025-7345 medium priority: Ubuntu including 1 source packages (gdk-pixbuf), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): released 8, ignored 1. https://ubuntu.com/security/CVE-2025-7345

Affected software / configurations for CVE-2025-7345

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-7345

cvelogic Threat Intelligence