---
id: CVE-2026-85715
title: ExifReader is a JavaScript Exif information parser
summary: >-
  ExifReader is a JavaScript Exif information parser. Prior to 4.41.1,
  ExifReader parses attacker-controlled HEIC or AVIF ISO-BMFF files in
  getItems() within src/image-header-iso-bmff-iloc.js and trusts iloc itemCount
  and extentCount value…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-789
  - CWE-835
vendor: mattiasw
product: ExifReader
affected:
  - ExifReader < 4.41.1
published: '2026-09-17'
updated: '2026-09-17'
sourceUpdated: '2026-09-17T16:18:15.790'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-85715'
references:
  - url: >-
      https://github.com/mattiasw/ExifReader/commit/17b901cd192d2c90d7f9f347bd3073b28b482699
    label: security-advisories@github.com
  - url: 'https://github.com/mattiasw/ExifReader/releases/tag/v4.41.1'
    label: security-advisories@github.com
  - url: >-
      https://github.com/mattiasw/ExifReader/security/advisories/GHSA-pj96-35fp-cfcc
    label: security-advisories@github.com
  - url: >-
      https://github.com/mattiasw/ExifReader/security/advisories/GHSA-pj96-35fp-cfcc
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
  - cve.org
  - exploit-available
exploitAvailable: true
ssvc:
  exploitation: poc
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-09-17T15:54:11.744033Z'
ingestedAt: '2026-09-17T16:21:47.712Z'
epss: 0.00609
epssPercentile: 0.46921
---

## Overview

ExifReader is a JavaScript Exif information parser. Prior to 4.41.1, ExifReader parses attacker-controlled HEIC or AVIF ISO-BMFF files in getItems() within src/image-header-iso-bmff-iloc.js and trusts iloc itemCount and extentCount values while allocating an extent object for every nested-loop iteration. When offsetSize, lengthSize, baseOffsetSize, and indexSize are zero, the extent fields consume no input bytes and the buffer offset does not advance, but the parser can still allocate up to itemCount multiplied by extentCount objects without an allocation budget. A small malicious iloc box can therefore cause hundreds of megabytes of heap growth or exhaust system memory, terminating a Node.js process and denying service to web, desktop, or mobile applications that parse untrusted images. The zero field widths are valid ISO-BMFF values indicating absent fields, so the vulnerable parser must bound work rather than relying on offset advancement. The issue is fixed in version 4.41.1.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.