CVE-2026-8814: ExifReader is vulnerable to denial of service via unbounded decompression of image metadata
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, compressediTXt, andiCCPchunks (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.
References
- gist.github.com/yuki-matsuhashi/cad1a45d936062438b4ab24613c34c55
- github.com/advisories/GHSA-rr89-w3h9-m66j
- github.com/mattiasw/ExifReader/commit/5f116128adc19f674902f8bf582bfe7dd0a36375
- github.com/mattiasw/ExifReader/security/advisories/GHSA-rr89-w3h9-m66j
- nvd.nist.gov/vuln/detail/CVE-2026-8814
- security.snyk.io/vuln/SNYK-JS-EXIFREADER-16689340
Code Behaviors & Features
Detect and mitigate CVE-2026-8814 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →