CVE-2026-40386 [Medium] | Integer Overflow in Libexif

CVE-2026-40386 is rated Low Risk (16.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

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

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-13

—

0.01%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.0	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. 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.4	2.5	[email protected]
7.1	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H` 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:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. 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:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.0

3.1

MEDIUM

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
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.4

2.5

[email protected]

7.1

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H 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:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.2

[email protected]

OS Trackers for CVE-2026-40386

vendor	priority	summary	link
`alpine`	—	CVE-2026-40386: 1 source package rows (libexif); 8 state rows across 2 repos (3.23-community, edge-community); fixed 0, open 8.	https://security.alpinelinux.org/vuln/CVE-2026-40386
`debian`	not yet assigned	CVE-2026-40386 not yet assigned priority: Debian including 1 source packages (libexif), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2026-40386
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2026-40386
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2026-40386/
`ubuntu`	medium	CVE-2026-40386 medium priority: Ubuntu including 1 source packages (libexif), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 8.	https://ubuntu.com/security/CVE-2026-40386

Affected software / configurations for CVE-2026-40386

Vendor	Product	Version	Raw CPE
libexif_project	libexif	<= 0.6.25	cpe:2.3:a:libexif_project:libexif::::::::

References for CVE-2026-40386

URL	Tags
https://github.com/libexif/libexif/commit/dc6eac6e9655d14d0779d99e82d0f5f442d2f34b	Patch

URL

CVE-2026-40386

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

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

Weakness enumeration for CVE-2026-40386

OS Trackers for CVE-2026-40386

Affected software / configurations for CVE-2026-40386

References for CVE-2026-40386