CVE-2026-94030: SerenityOS LibGfx BMPLoader.cpp decode_bmp_pixel_data integer overflow
A security vulnerability has been detected in SerenityOS up to 3d83e4509fd20d7438e1ae8470ffe668c136229c. Affected by this vulnerability is the function decodebmppixeldata of the file Userland/Libraries/LibGfx/ImageFormats/BMPLoader.cpp of the component LibGfx. The manipulation of the argument height leads to integer overflow. The attack is possible to be carried out remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The exploit has been disclosed publicly and may be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The identifier of the patch is 007041bb2dd6d140c9e707caddfb0a49ecf96469. Applying a patch is the recommended action to fix this issue. This was reproducible with a minimal 55-byte PoC via the standard image-decode fuzz target but evidence for an actual exploitable defect is thin.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
SerenityOS LibGfx (Userland/Libraries/LibGfx/ImageFormats/BMPLoader.cpp)to a version that resolves this vulnerability.Patch 007041bb2dd6d140c9e707caddfb0a49ecf96469
Event History
Frequently Asked Questions
What conditions are required for exploitation?
An attacker would need to induce decoding of a BMP with a manipulated height value. The vector is remote, but user interaction is required and the attack complexity is rated high.
How can I determine whether my source tree is affected?
The issue affects SerenityOS revisions up to 3d83e4509fd20d7438e1ae8470ffe668c136229c. Check whether patch commit 007041bb2dd6d140c9e707caddfb0a49ecf96469 has been applied.
What should be done if the affected code is present?
Apply patch 007041bb2dd6d140c9e707caddfb0a49ecf96469. Because SerenityOS uses a rolling release model, affected and fixed release version numbers are not available.
How urgent is this in practice?
The issue is rated low severity, with availability impact only, and exploitation is considered difficult. A public exploit disclosure exists, but the available evidence for an actually exploitable defect is described as thin.