CVE-2026-8814: Exifreader Denial of Service Vulnerability

MODERATE
Advisory Identifier: GHSA-rr89-w3h9-m66j
CVSS 5.3
CWE-409
Published
Advisory Summary

CVE-2026-8814 is a MODERATE (CVSS 5.3) denial of service vulnerability (CWE-409: Improper Handling of Highly Compressed Data (Data Amplification)) affecting Exifreader libraries in the npm ecosystem. The issue involves exifreader is vulnerable to denial of service via unbounded decompression of image metadata. Remediation is available by upgrading affected packages to version 4.39.0.

CVE-2026-8814 at a Glance

CVE Identifier CVE-2026-8814
GHSA Identifier GHSA-rr89-w3h9-m66j
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-409: Improper Handling of Highly Compressed Data (Data Amplification)
Affected Product Exifreader
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability Low (A:L)

How to Fix CVE-2026-8814

To remediate this vulnerability, upgrade all affected Exifreader dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

exifreader fixed: 4.39.0
npm install exifreader@4.39.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls exifreader

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-8814, inspect your project dependencies using npm:

npm ls exifreader

Analyze the terminal output to locate any version of Exifreader in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.39.0), your application is affected.

Note: The npm ls exifreader command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-409: Improper Handling of Highly Compressed Data (Data Amplification), where the product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output. In Exifreader, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Versions of ExifReader from 4.20.0 through 4.38.1 do not bound the size of decompressed metadata blocks. When a caller invokes the asynchronous API (e.g. `ExifReader.load(file)` or `ExifReader.load(buffer, {async: true})`) on an attacker-supplied image, a small compressed chunk in the file can expand to hundreds of megabytes of memory, consuming heap and CPU until the process slows down or runs out of memory. The affected paths share a single decompression utility, so the issue is reachable through any compressed metadata block the library handles asynchronously, including: - PNG `zTXt`, compressed `iTXt`, and `iCCP` chunks (deflate) - JPEG XL Brotli-compressed Exif and XMP blocks A typical proof of concept produced roughly 1000× expansion (for example, ~32 KB of compressed input expanded to ~32 MB of output, ~130 KB to ~128 MB). Both the npm package and the `dist/` bundle published from this repository (consumed by Bower and other users of the prebuilt artifact) are affected. ### Patches Fixed in **4.39.0**. The decompression utility now reads the decompressed stream incrementally and aborts as soon as the running total would exceed a configurable limit. The default cap is **128 MiB** per metadata block, which is well above any realistic legitimate value. When a block exceeds the cap, that block is skipped (a warning is emitted via `console.warn`) and the remaining tags are returned as usual. The cap is configurable via the new `maxDecompressedSize` field on the `decompress` option, in bytes: ```javascript const tags = await ExifReader.load(file, { async: true, decompress: { maxDecompressedSize: 16 * 1024 * 1024 // 16 MiB } }); ``` The same cap applies to results returned by user-supplied custom `brotli`/`deflate` functions. ### Workarounds - If upgrading is not possible, avoid invoking the asynchronous API on untrusted inputs. The synchronous code path skips compressed metadata blocks entirely and is not affected. Alternatively, pre-validate input files by source or size before passing them to ExifReader. ### Resources - Patch: https://github.com/mattiasw/ExifReader/commit/5f116128adc19f674902f8bf582bfe7dd0a36375 - README — "Limiting decompressed metadata size": https://github.com/mattiasw/ExifReader/blob/main/README.md#limiting-decompressed-metadata-size

CVE-2026-8814 Affected Exifreader Versions

1 component(s)
Fixed Versions:
4.39.0
Product / Package Ecosystem Affected Versions Fixed Version
exifreader
npm
≥ 4.20.0
< 4.39.0
4.39.0

References

Frequently Asked Questions

What is CVE-2026-8814?
CVE-2026-8814 is a security vulnerability in Exifreader involving ExifReader is vulnerable to denial of service via unbounded decompression of image metadata under CWE-409: Improper Handling of Highly Compressed Data (Data Amplification).
Which Exifreader versions are affected?
Affected versions include releases prior to 4.39.0 across affected packages: exifreader.
What version fixes CVE-2026-8814?
Upgrading to 4.39.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is exifreader affected?
Yes, exifreader is affected in releases prior to 4.39.0. Upgrade your dependency to 4.39.0 or later.
What is the CVSS score of CVE-2026-8814?
CVE-2026-8814 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2026-8814?
CVE-2026-8814 is classified under CWE-409: Improper Handling of Highly Compressed Data (Data Amplification) (The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.).
How can I check npm dependencies for CVE-2026-8814?
Run the dependency tree command: 'npm ls exifreader'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rr89-w3h9-m66j",
  "modified" : "2026-07-17T16:52:29Z",
  "published" : "2026-05-29T17:52:26Z",
  "aliases" : [ "CVE-2026-8814" ],
  "summary" : "ExifReader is vulnerable to denial of service via unbounded decompression of image metadata",
  "details" : "### Impact\n\nVersions of ExifReader from 4.20.0 through 4.38.1 do not bound the size of decompressed metadata blocks. When a caller invokes the asynchronous API (e.g. `ExifReader.load(file)` or `ExifReader.load(buffer, {async: true})`) on an attacker-supplied image, a small compressed chunk in the file can expand to hundreds of megabytes of memory, consuming heap and CPU until the process slows down or runs out of memory.\n\nThe affected paths share a single decompression utility, so the issue is reachable through any compressed metadata block the library handles asynchronously, including:\n\n- PNG `zTXt`, compressed `iTXt`, and `iCCP` chunks (deflate)\n- JPEG XL Brotli-compressed Exif and XMP blocks\n\nA typical proof of concept produced roughly 1000× expansion (for example, ~32 KB of compressed input expanded to ~32 MB of output, ~130 KB to ~128 MB).\n\nBoth the npm package and the `dist/` bundle published from this repository (consumed by Bower and other users of the prebuilt artifact) are affected.\n\n### Patches\n\nFixed in **4.39.0**. The decompression utility now reads the decompressed stream incrementally and aborts as soon as the running total would exceed a configurable limit. The default cap is **128 MiB** per metadata block, which is well above any realistic legitimate value. When a block exceeds the cap, that block is skipped (a warning is emitted via `console.warn`) and the remaining tags are returned as usual.\n\nThe cap is configurable via the new `maxDecompressedSize` field on the `decompress` option, in bytes:\n\n```javascript\nconst tags = await ExifReader.load(file, {\n    async: true,\n    decompress: {\n        maxDecompressedSize: 16 * 1024 * 1024 // 16 MiB\n    }\n});\n```\n\nThe same cap applies to results returned by user-supplied custom `brotli`/`deflate` functions.\n\n### Workarounds\n\n- If upgrading is not possible, avoid invoking the asynchronous API on untrusted inputs. The synchronous code path skips compressed metadata blocks entirely and is not affected. Alternatively, pre-validate input files by source or size before passing them to ExifReader.\n\n### Resources\n\n- Patch: https://github.com/mattiasw/ExifReader/commit/5f116128adc19f674902f8bf582bfe7dd0a36375\n- README — \"Limiting decompressed metadata size\": https://github.com/mattiasw/ExifReader/blob/main/README.md#limiting-decompressed-metadata-size",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "exifreader"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.20.0"
      }, {
        "fixed" : "4.39.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/mattiasw/ExifReader/security/advisories/GHSA-rr89-w3h9-m66j"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-8814"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mattiasw/ExifReader/commit/5f116128adc19f674902f8bf582bfe7dd0a36375"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/mattiasw/ExifReader"
  }, {
    "type" : "WEB",
    "url" : "https://security.snyk.io/vuln/SNYK-JS-EXIFREADER-16689340"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-409" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-29T17:52:26Z",
    "nvd_published_at" : "2026-05-19T07:16:30Z"
  }
}