A flaw was found in GIMP when processing XCF image files

CVE-2025-48798 is a use-after-free in xcf_load_image() inside app/xcf/xcf-load.c, the loader for GIMP's native XCF file format. A malformed XCF can free an object and then have GIMP dereference the stale pointer, giving the attacker a shot at arbitrary code execution in the context of the user running GIMP. It affects GIMP 2.10.x through 2.10.38 and was fixed in 2.10.40 upstream, with backports in Debian bookworm (2.10.34-1+deb12u3), Debian bullseye LTS (2.10.22-4+deb11u3), SUSE (2.10.30-150400.3.20.1), and Mageia.

The vendor HIGH (7.3) rating is technically defensible per the CVSS vector (AV:L/AC:L/PR:L/UI:R) but overstates operational risk. XCF is a proprietary GIMP-only container; users almost never receive .xcf files from untrusted sources the way they do PDFs, Office docs, or PNGs. Delivery friction is high, the blast radius is a single desktop user account, and there is no server-side or headless GIMP footprint in a typical enterprise. This is a MEDIUM for practical purposes.

Why this verdict

• Local + UI:R gate: The CVSS vector itself concedes this needs a user to double-click a hand-crafted XCF. No wormability, no drive-by, no server component.
• Proprietary file format: XCF is GIMP-only. Users don't routinely email XCFs — unlike PDFs or Office docs, an unsolicited .xcf attachment is inherently suspicious and easy to policy-block at the mail gateway.
• Blast radius = one user account: Code executes as the invoking user, no service/daemon context. Role multiplier: GIMP is 100% workstation software — there is no domain controller, CI runner, hypervisor, or identity-provider role for this component. The role floor is (a) low-value desktop, so no HIGH/CRITICAL role floor applies.
• No KEV, EPSS 0.0017: Zero real-world exploitation signal seven months post-disclosure.
• Modern mitigations bite hard: ASLR, RELRO, FORTIFY_SOURCE, EDR behavioral detection on gimp → shell all substantially raise exploit cost.
• Patch is trivial: Distro package update, no downtime, no dependency risk — the 365-day remediation window is more than adequate.

Why not higher?

HIGH would imply a chain that either bypasses user interaction, hits a server role, or has active exploitation. None of those apply: UI:R is mandatory, GIMP has no server surface, EPSS is near-zero, and KEV does not list it. The vendor's 7.3 mechanically follows CVSS scoring but ignores that XCF is not a plausible delivery vector at enterprise scale.

Why not lower?

LOW/IGNORE is wrong because this is a remote-code-execution primitive on a still-widely-installed desktop tool. Targeted actors going after design shops, game studios, or high-value open-source contributors have a credible use case for this. Backlog-only treatment (LOW) would ignore the credential-theft-from-workstation follow-on.

1. Block .xcf attachments at the email gateway — XCF has no legitimate business use in email for 95%+ of organizations. Add .xcf to Proofpoint/Mimecast/M365 mail-flow attachment blocklists. No mitigation SLA at MEDIUM — implement opportunistically within the 365-day remediation window.
2. Push GIMP patch via existing endpoint software management — Roll upstream 2.10.40 or the distro-backported package (Debian 2.10.34-1+deb12u3, SUSE 2.10.30-150400.3.20.1) through Intune/Jamf/Ansible/unattended-upgrades. Standard 365-day remediation SLA — bundle with next quarterly workstation image refresh.
3. EDR rule: alert on gimp spawning shells or network utilities — Detect post-exploitation with a behavioral rule that fires when the gimp process creates a child bash, sh, powershell, curl, wget, nc, python. This catches this CVE and any future GIMP parser bug.
4. Restrict GIMP install to roles that need it — Design, marketing, and engineering-artwork users typically. Remove GIMP from finance/HR/exec workstations via app-inventory tooling — you don't need to patch what isn't installed.

Run on each Linux/macOS workstation (or push via your config-management tool) as any user. Invoke: bash check-gimp-cve-2025-48798.sh. No root required — reads GIMP version from the binary and compares against the fixed threshold.

#!/usr/bin/env bash
# check-gimp-cve-2025-48798.sh
# Detects vulnerable GIMP installations for CVE-2025-48798 (XCF UAF)
# Exit codes: 0 PATCHED, 1 VULNERABLE, 2 UNKNOWN
set -u

FIXED_UPSTREAM="2.10.40"
FIXED_DEB12="2.10.34-1+deb12u3"
FIXED_DEB11="2.10.22-4+deb11u3"

ver_ge() {
  # returns 0 if $1 >= $2 using dpkg --compare-versions if available, else sort -V
  if command -v dpkg >/dev/null 2>&1; then
    dpkg --compare-versions "$1" ge "$2"
    return $?
  fi
  [ "$(printf '%s\n%s\n' "$2" "$1" | sort -V | head -n1)" = "$2" ]
}

GIMP_BIN="$(command -v gimp || command -v gimp-2.10 || true)"
if [ -z "$GIMP_BIN" ]; then
  echo "PATCHED: GIMP not installed"
  exit 0
fi

# Prefer distro package version when available (captures backports)
PKG_VER=""
if command -v dpkg-query >/dev/null 2>&1; then
  PKG_VER="$(dpkg-query -W -f='${Version}' gimp 2>/dev/null || true)"
elif command -v rpm >/dev/null 2>&1; then
  PKG_VER="$(rpm -q --qf '%{VERSION}-%{RELEASE}' gimp 2>/dev/null || true)"
fi

UPSTREAM_VER="$($GIMP_BIN --version 2>/dev/null | awk '{print $NF}')"
if [ -z "$UPSTREAM_VER" ]; then
  echo "UNKNOWN: could not determine GIMP version"
  exit 2
fi

echo "Detected GIMP upstream version: $UPSTREAM_VER"
[ -n "$PKG_VER" ] && echo "Detected distro package version: $PKG_VER"

# Backport check for Debian bookworm / bullseye
if [ -n "$PKG_VER" ] && command -v dpkg >/dev/null 2>&1; then
  if dpkg --compare-versions "$PKG_VER" ge "$FIXED_DEB12" 2>/dev/null; then
    echo "PATCHED: distro-backport $PKG_VER >= $FIXED_DEB12"
    exit 0
  fi
  if dpkg --compare-versions "$PKG_VER" ge "$FIXED_DEB11" 2>/dev/null; then
    echo "PATCHED: distro-backport $PKG_VER >= $FIXED_DEB11"
    exit 0
  fi
fi

if ver_ge "$UPSTREAM_VER" "$FIXED_UPSTREAM"; then
  echo "PATCHED: upstream $UPSTREAM_VER >= $FIXED_UPSTREAM"
  exit 0
fi

echo "VULNERABLE: GIMP $UPSTREAM_VER is below fixed upstream $FIXED_UPSTREAM and no recognized backport detected"
exit 1

Sources

1. NVD — CVE-2025-48798
2. Red Hat Security — CVE-2025-48798
3. Wiz Vulnerability DB — CVE-2025-48798
4. Debian Security Tracker — gimp
5. Debian DSA-5939-1
6. Debian LTS DLA 4342-1
7. Mageia MGASA-2026-0012
8. SUSE openSUSE-SU-2025:02164-1