# CVE-2026-81893: Gdk-pixbuf: gdk-pixbuf: invalid write in jpeg icc profile parser on error recovery

> An attacker can cause a denial of service by tricking an application into processing a malicious JPEG image with crafted ICC profile markers.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** AZL-98370, BELL-CVE-2026-81893, DEBIAN-CVE-2026-81893, ECHO-b76b-475e-7ef9, GHSA-237w-6c39-25rh, OESA-2026-3773, UBUNTU-CVE-2026-81893

## What is CVE-2026-81893?

CVE-2026-81893 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 27 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-81893?


## How do I fix CVE-2026-81893?

Apply the vendor's patch.

## Is CVE-2026-81893 being exploited?

There is no known exploitation of CVE-2026-81893 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81893 and fix it if it is affected.

What it is: CVE-2026-81893 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 27 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-81893 in the wild and no public exploit code.

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-2026-81893/ (Markdown: https://insights.sbomify.com/CVE-2026-81893/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81893
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81893
- OSV: https://osv.dev/vulnerability/CVE-2026-81893

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81893/
Summaries are generated and may contain mistakes; the official description above is the record.