CVE-2026-35444 [High] | Out-of-bounds Read in Sdl Image

SDL_image is a library to load images of various formats as SDL surfaces. In do_layer_surface() in src/IMG_xcf.c, pixel index values from decoded XCF tile data are used directly as colormap indices without validating them against the colormap size (cm_num). A crafted .xcf file with a small colormap and out-of-range pixel indices causes heap out-of-bounds reads of up to 762 bytes past the colormap allocation. Both IMAGE_INDEXED code paths are affected (bpp=1 and bpp=2). The leaked heap bytes are written into the output surface pixel data, making them potentially observable in the rendered image. This vulnerability is fixed with commit 996bf12888925932daace576e09c3053410896f8.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-07	—	0.01%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-07

—

0.01%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.1	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	2.8	4.2	[email protected]
6.1	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	1.8	4.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.1

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

2.8

4.2

[email protected]

6.1

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

1.8

4.2

[email protected]

OS Trackers for CVE-2026-35444

vendor	priority	summary	link
`alpine`	—	CVE-2026-35444: 1 source package rows (sdl_image); 3 state rows across 2 repos (3.23-community, edge-community); fixed 0, open 3.	https://security.alpinelinux.org/vuln/CVE-2026-35444
`debian`	not yet assigned	CVE-2026-35444 not yet assigned priority: Debian including 3 source packages (libsdl2-image, libsdl3-image, sdl-image1.2), 13 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 9, resolved 4.	https://security-tracker.debian.org/tracker/CVE-2026-35444
`ubuntu`	medium	CVE-2026-35444 medium priority: Ubuntu including 3 source packages (libsdl2-image, libsdl3-image, sdl-image1.2), 20 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 18, DNE 2.	https://ubuntu.com/security/CVE-2026-35444

Affected software / configurations for CVE-2026-35444

Vendor	Product	Version	Raw CPE
libsdl	sdl_image	< 2026-04-02	cpe:2.3:a:libsdl:sdl_image::::::::

References for CVE-2026-35444

URL	Tags
https://github.com/libsdl-org/SDL_image/security/advisories/GHSA-gq8w-x74c-h6p7	Vendor Advisory Patch

URL

CVE-2026-35444 | SDL_image has a heap buffer overflow READ via unchecked colormap index in XCF loader

Exploit prediction scoring system (EPSS) score for CVE-2026-35444

Common vulnerability scoring system (CVSS) metrics for CVE-2026-35444

Weakness enumeration for CVE-2026-35444

OS Trackers for CVE-2026-35444

Affected software / configurations for CVE-2026-35444

References for CVE-2026-35444