Security Resilience

CVE-2026-40385

Memory Safety in Libexif Project Libexif ≤ 0.6.25

Published
12 April 2026
Modified
14 April 2026
Patch / advisory
CVSS Score v3.1 4.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L
EPSS Score 0.0013 2th percentile
Risk Priority 31 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-40385 is a medium-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Libexif Project Libexif. Its CVSS base score is 4.0 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-40385 is an unsigned 32-bit integer overflow in the Nikon MakerNote handling functionality of libexif through version 0.6.25. This vulnerability, classified as CWE-190, affects only 32-bit systems and carries a CVSS v3.1 base score of 4.0 (AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L). It was published on 2026-04-12.

Local attackers can exploit this issue to trigger crashes or information leaks in applications using the affected libexif code. Exploitation requires local access, high attack complexity, no privileges, and no user interaction. Successful attacks result in low-impact confidentiality loss or availability disruption, with no integrity impact and unchanged scope.

The libexif project mitigates this vulnerability through a specific commit available at https://github.com/libexif/libexif/commit/93003b93e50b3d259bd2227d8775b73a53c35d58. Security practitioners should update libexif beyond version 0.6.25 on 32-bit systems to apply the fix.

EU & UK References

Vulnerability Data

In libexif through 0.6.25, an unsigned 32bit integer overflow in Nikon MakerNote handling could be used by local attackers to cause crashes or information leaks. This only affects 32bit systems.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-32775Same product: Libexif Project Libexif
CVE-2026-40386Same product: Libexif Project Libexif
CVE-2024-38624Shared CWE-190
CVE-2025-22471Shared CWE-190
CVE-2026-25208Shared CWE-190
CVE-2026-42199Shared CWE-190
CVE-2026-64694Shared CWE-190
CVE-2026-11725Shared CWE-190
CVE-2025-29072Shared CWE-190
CVE-2026-20339Shared CWE-190

Affected Assets

libexif project
libexif
≤ 0.6.25

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.2.6

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.

Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.

Input validation enforces bounds on values before arithmetic, stopping the conditions that trigger overflow or wraparound.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect integer overflows before release.

prevents

Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.

References