LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32775: libexif through 0.6.25 has a flaw in decoding MakerNotes.

libexif through 0.6.25 has a flaw in decoding MakerNotes. If the exif_mnote_data_get_value function gets passed in a 0 size, the passed in-buffer would be overwritten due to an integer underflow.

HighCVSS 7.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-32775 is a high-severity memory corruption flaw in libexif, a library used to read photo metadata. A crafted or malformed image metadata path could cause buffer overwrites when MakerNotes are decoded. Organizations should prioritize systems and applications that process untrusted images.

Executive priority

Treat as a near-term remediation item for image-processing environments, especially internet-facing upload pipelines or products handling untrusted photos. Prioritize inventory first because libexif is often embedded indirectly through applications and distributions.

Technical view

libexif through 0.6.25 has an integer underflow (CWE-191) in exif_mnote_data_get_value when size is zero, causing the supplied in-buffer to be overwritten during MakerNotes decoding. The CVSS 3.1 score is 7.4 with high confidentiality, integrity, and availability impact, but high attack complexity.

Likely exposure

Exposure is most likely in desktop, server, container, or embedded applications that link libexif and parse EXIF MakerNotes from user-supplied or externally sourced images. The source bundle does not identify downstream products or packaged fixed versions.

Exploitation context

The provided CVE data does not indicate CISA KEV listing or active exploitation. Public references include a GitHub issue and a fixing commit. The CVSS vector lists local attack vector and high complexity, so practical exploitation may require specific processing conditions.

Researcher notes

Evidence is limited to the CVE record, GitHub issue, and commit. No exploit proof, KEV entry, or downstream affected-product list is provided. Validate impact in context without publishing weaponized inputs or reproduction details.

Mitigation direction

  • Inventory libexif use across applications, packages, containers, and embedded builds.
  • Upgrade to a vendor release that includes the upstream fix when available.
  • If building from source, review the referenced upstream commit with standard change-control.
  • Reduce or isolate processing of untrusted image metadata where practical.
  • Monitor operating system and application vendor advisories for packaged fixes.

Validation and detection

  • Confirm whether installed libexif versions are 0.6.25 or earlier.
  • Check whether the referenced upstream commit is present in deployed source or packages.
  • Identify services accepting or processing externally supplied image files.
  • Review crash, memory-corruption, or sanitizer findings around EXIF MakerNotes parsing.
  • Track vendor advisories for fixed package names and versions.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-191: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32775 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H1.45.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2026-32775Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
libexif projectlibexif0unknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-191 · source CWE mapping

Integer Underflow (Wrap or Wraparound)

Integer Underflow (Wrap or Wraparound) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.