CVSS 4.0
8.5 highCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NHigh (8.5) in fltk fltk. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExplain CVE-2026-116724 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116724?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116724?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116724 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| fltk | through 1.4.5 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | fltk1.3 | no fix listed | DEBIAN-CVE-2026-116724 |
| Debian | 13 | fltk1.3, fltk1.4 | no fix listed | DEBIAN-CVE-2026-116724 |
| Debian | 14 | fltk1.3 | 1.3.11-4 | DEBIAN-CVE-2026-116724 |
| Debian | 14 | fltk1.4 | 1.4.5-1 | DEBIAN-CVE-2026-116724 |
| Ubuntu | 16.04:LTS, 18.04:LTS, 20.04:LTS and 2 more | fltk1.3 | no fix listed | UBUNTU-CVE-2026-116724 |
| Ubuntu | 26.04:LTS, 26.10 | fltk1.3, fltk1.4 | no fix listed | UBUNTU-CVE-2026-116724 |
| openSUSE | Tumbleweed | fltk | 1.3.11-2.1 | openSUSE-SU-2026:12362-1 |
| Azure Linux | 3 | fltk | no fix listed | AZL-111109 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.
Red Hat rates this Important.
This vulnerability is rated as an Important severity flaw because successful exploitation could lead to arbitrary code execution within the context of the running application or cause an application crash. In Red Hat Enterprise Linux environments, the FLTK library is used by desktop graphical utilities to render graphical assets. Triggering the flaw requires a user to open an untrusted bitmap or icon file using an application built against the affected toolkit. While exploitation is limited to local user interaction, the potential compromise of confidentiality, integrity, and availability justifies the Important rating.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
--- CME Mitigation Guidance (2026-11-02) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to cast image dimensions to size_t and validate colormap size bounds prior to heap buffer allocation in Fl_BMP_Image to prevent integer overflows and out-of-bounds writes: upgrade to FLTK 1.5.0 (or the fixed Fltk/Giac builds), which return ERR_FORMAT if colors_used exceeds 256 and cast width to size_t during image array allocation to prevent integer overflow, closing all 2 injection vectors (crafted BMP image file, crafted ICO image file). Until patched, this is a concern on Applications built against FLTK through 1.4.5 handling user-supplied BMP or ICO files, so Prevent users from opening untrusted BMP or ICO files with desktop utilities linked against vulnerable FLTK builds. As a compensating measure, Randomize user-space heap and library memory layout to hinder reliable code execution via heap corruption, Harden executable binaries with full RELRO and PIE to prevent relocation table overwrites during heap exploitation, Restrict indirect call targets using Control Flow Integrity to mitigate hijacked control flow from corrupted function pointers, and Enforce non-executable heap memory pages to block execution of payload code written to the heap buffer. These controls limit blast radius and contain exploitation, but they do not fix the underlying integer overflow defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-119 Compiler Integer Overflow and Conversion Safety (-ftrapv / UBSan Integer) (high)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 7 | fltk | Affected | |
| Red Hat Enterprise Linux 8 | fltk | Affected | |
| Red Hat Enterprise Linux 9 | fltk | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-116724.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.