# CVE-2026-116724: FLTK through 1.4.5 Heap Buffer Overflow via Fl_BMP_Image Integer Overflow


- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-111109, DEBIAN-CVE-2026-116724, GHSA-vc45-5x28-58gf

## What is CVE-2026-116724?

CVE-2026-116724 is a high-severity vulnerability in fltk, published on 26 Oct 2026. 

### Official description

FLTK through 1.4.5 contains an integer overflow vulnerability in Fl_BMP_Image::load_bmp_() that causes undersized pixel buffer allocation from file-supplied width and height. Attackers can supply a crafted BMP or ICO file with large dimensions so row decoding writes file-derived data past the heap buffer, corrupting the application heap.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

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

## Is CVE-2026-116724 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116724 is a high-severity vulnerability in fltk, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116724 in the wild and no public exploit code.

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

## Sources

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

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