# CVE-2026-32775: Integer overflow in libexif

> An integer underflow in libexif allows attackers to overwrite buffers via crafted EXIF data, potentially leading to code execution or crashes.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Mar 2026
- **Updated:** 12 Apr 2026
- **Also known as:** AZL-79862, BELL-CVE-2026-32775, DEBIAN-CVE-2026-32775, GHSA-pq8m-942f-68cv, JLSEC-2026-150, OESA-2026-1678, UBUNTU-CVE-2026-32775

## What is CVE-2026-32775?

CVE-2026-32775 is a high-severity vulnerability in libexif, published on 16 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound))

## Which versions are affected by CVE-2026-32775?

It affects 1 product.


Products: Libexif Project Libexif.

## How do I fix CVE-2026-32775?

Upgrade to a fixed version.

## Is CVE-2026-32775 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32775 exists.

## Other vulnerabilities in libexif

- [CVE-2017-7544](https://insights.sbomify.com/CVE-2017-7544/): Information disclosure in libexif (critical 9.1)
- [CVE-2018-20030](https://insights.sbomify.com/CVE-2018-20030/): Denial of service in libexif (high 7.5)
- [CVE-2012-2814](https://insights.sbomify.com/CVE-2012-2814/): Memory corruption in n/a (high 7.5)
- [CVE-2012-2840](https://insights.sbomify.com/CVE-2012-2840/): Integer overflow in n/a (high 7.5)
- [CVE-2012-2841](https://insights.sbomify.com/CVE-2012-2841/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32775 and fix it if it is affected.

What it is: CVE-2026-32775 is a high-severity vulnerability in libexif, published on 16 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32775 exists.

Affected product: libexif. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32775/ (Markdown: https://insights.sbomify.com/CVE-2026-32775/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32775
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32775
- OSV: https://osv.dev/vulnerability/CVE-2026-32775

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32775/
Summaries are generated and may contain mistakes; the official description above is the record.