# CVE-2026-111149: FreeImage through 3.19.23 Heap Out-of-Bounds Read via PICT Unpack32Bits

> Attackers can leak heap memory or crash the application by supplying a crafted PICT image file to the FreeImage library.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **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:** No
- **Published:** 15 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-hmpq-mc7h-9mv3

## What is CVE-2026-111149?

CVE-2026-111149 is a medium-severity vulnerability in FreeImage, published on 15 Oct 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

FreeImage (danoli3 fork) through 3.19.23 contains a heap out-of-bounds read vulnerability in Unpack32Bits() in PluginPICT.cpp because rowBytes is never checked against the file-controlled PixMap width. Attackers can supply a crafted PICT file with a truncated or undersized rowBytes to over-read up to 64 KiB of heap, leaking memory into decoded pixels or crashing the process.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

No fix has been published for CVE-2026-111149 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111149 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111149 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111149 is a medium-severity vulnerability in FreeImage, published on 15 Oct 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111149 exists.

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

## Sources

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

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