CVE-2025-7345
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA heap buffer overflow vulnerability exists in gdk-pixbuf's JPEG image loading function (gdk_pixbuf__jpeg_image_load_increment in io-jpeg.c) and glib's Base64 encoding function (g_base64_encode_step in glib/gbase64.c). When processing a maliciously crafted JPEG image, the Base64 encoding process can read beyond allocated heap buffer boundaries, causing out-of-bounds memory access that may lead to crashes or potentially arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check gdk-pixbuf versionRun `pkg-config --modversion gdk-pixbuf-2.0` or check your package manager for gdk-pixbuf versionAffected if The installed version is older than the patched version of gdk-pixbuf that addresses CVE-2025-7345
-
Check glib versionRun `pkg-config --modversion glib-2.0` or check your package manager for glib versionAffected if The installed version is older than the patched version of glib that addresses CVE-2025-7345
-
Verify gdk-pixbuf JPEG loader is presentCheck for the JPEG loader module: look in /usr/lib/gdk-pixbuf-2.0/loaders/ or run `gdk-pixbuf-query-loaders --verbose 2>/dev/null | grep -i jpeg`Affected if The JPEG loader exists and is loaded, meaning gdk-pixbuf can process JPEG images
-
Identify processes using gdk-pixbuf for image loadingRun `lsof 2>/dev/null | grep -i pixbuf` or audit system processes that handle image files from untrusted sourcesAffected if Applications that process untrusted JPEG images using gdk-pixbuf are running on the system
The system is affected if it runs a version of gdk-pixbuf or glib older than their patched versions AND processes JPEG images from untrusted sources using gdk-pixbuf functionality.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate gdk-pixbuf and glib libraries to patched versions. Until patches are applied, restrict processing of untrusted JPEG images and implement input validation to mitigate exploitation risk.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7345 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data