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.2% 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-116723 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116723?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116723?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-116723 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-116723 |
| Debian | 13 | fltk1.3, fltk1.4 | no fix listed | DEBIAN-CVE-2026-116723 |
| Debian | 14 | fltk1.3 | 1.3.11-4 | DEBIAN-CVE-2026-116723 |
| Debian | 14 | fltk1.4 | 1.4.5-1 | DEBIAN-CVE-2026-116723 |
| Ubuntu | 16.04:LTS, 18.04:LTS, 20.04:LTS and 2 more | fltk1.3 | no fix listed | UBUNTU-CVE-2026-116723 |
| Ubuntu | 26.04:LTS, 26.10 | fltk1.3, fltk1.4 | no fix listed | UBUNTU-CVE-2026-116723 |
| openSUSE | Tumbleweed | fltk | 1.3.11-2.1 | openSUSE-SU-2026:12362-1 |
| Azure Linux | 3 | fltk | no fix listed | AZL-111106 |
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.
Red Hat has rated this vulnerability as having an Important severity because successful exploitation could permit arbitrary code execution with the privileges of the local user running the vulnerable application, even though triggering the flaw requires user interaction to open an untrusted image. FLTK is distributed as an optional graphical user interface development toolkit rather than a core system service or network-facing daemon, limiting the attack surface to client-side applications that directly parse unvalidated bitmap or icon files. Headless installations and standard server deployments that do not run FLTK-linked software are not exposed to this issue.
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 validate the colors_used header field against the fixed 256-entry colormap array boundary in Fl_BMP_Image::load_bmp_() before reading palette data: upgrade to FLTK 1.5.0 (or the fixed Fltk/Giac builds), which reject files specifying a colors_used value greater than 256 with an ERR_FORMAT error and cast width to size_t during pixel array allocation, closing all 2 injection vectors (crafted BMP image file, crafted ICO image file). Until patched, this is only a concern on Client applications linked against FLTK parsing untrusted image files — Headless installations and server deployments not running FLTK-linked software are unaffected — so Prevent users and services from opening or processing untrusted BMP or ICO image files within FLTK-linked applications. As a compensating measure, Enable Address Space Layout Randomization to randomize stack and library addresses and disrupt payload construction, Enable Full RELRO and PIE to randomize base executable addresses and harden the Global Offset Table, Enforce Control Flow Integrity and shadow call stacks to protect return addresses and validate indirect branches, Compile with FORTIFY_SOURCE to substitute bounds-checked functions that abort when writes exceed fixed buffer bounds, and Enforce non-executable stack memory via NX/XD bits to prevent direct execution of injected shellcode. These controls limit blast radius and contain exploitation, but they do not fix the underlying stack-based buffer overflow — apply the upstream patch to fully remediate.
Highest-impact CME: CME-103 Stack Canaries (Stack Protector) (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-116723.