Skip to content
statance
MenuClose
medium · CVSS 4.7

CVE-2026-81893

Gdk-pixbuf: gdk-pixbuf: invalid write in jpeg icc profile parser on error recovery

Published 27 Aug 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-06 01:53 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A flaw was found in gdk-pixbuf. When loading a specially crafted JPEG image containing chunked ICC profile markers, an error during ICC profile parsing can leave stale size metadata after the profile buffer is freed. A subsequent allocation in the same decode can cause an out-of-bounds write, potentially crashing the application. To exploit this flaw, an application using gdk-pixbuf must process the malicious JPEG image.

Affected version >= 2.26.4

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
gdk-pixbuf2Red HatDefault status: affectedSee vendor advisory
glycin-loadersRed HatDefault status: unaffectedSee vendor advisory
loupeRed HatDefault status: unaffectedSee vendor advisory
snapshotRed HatDefault status: unaffectedSee vendor advisory
gdk-pixbuf2Red HatDefault status: unaffectedSee vendor advisory
gdk-pixbuf2Red HatDefault status: affectedSee vendor advisory
gdk-pixbuf2Red HatDefault status: affectedSee vendor advisory
gdk-pixbuf2Red HatDefault status: affectedSee vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed