probe-image-size memory exhaustion in WebP EXIF chunk parsing
- Exploited
- No known exploitation
- Fix
- Fixed in 7.5.0
- Who is exposed
- Not reported
Summary
probe-image-size, a Node.js image-probing package, can be made to exhaust memory when it parses a WebP image. A remote attacker who can supply a WebP stream or URL without logging in can declare an oversized EXIF chunk, causing unbounded buffering that can crash the process.
Written by a model
Original description
probe-image-size before 7.5.0 contains an unbounded memory buffering vulnerability in parseExif in lib/parse_stream/webp.js that allows remote attackers to exhaust memory via an attacker-declared EXIF chunk length. Attackers can supply a WebP stream or URL to probe(url) or probe(stream) declaring a huge EXIF length after VP8X, causing unbounded buffering and process memory exhaustion.
What to do
Upgrade to a fixed version: 7.5.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134166 (probe-image-size before 7.5.0 Memory Exhaustion via WebP EXIF Chunk Length), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134166 (entry last updated 2026-11-20):
Affected:
- npm package probe-image-size: fixed in 7.5.0
Fixed versions: 7.5.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-134166 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134166 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nodeca/probe-image-size/security/advisories/GHSA-5v8x-rm7w-m4c7
- https://github.com/nodeca/probe-image-size/commit/d91678eaff2aad93f7b05bc5212b75856164ec7a
- https://github.com/nodeca/probe-image-size/blob/64565c3c8b4b69655426cdfce250e6a93455c9da/lib/parse_stream/webp.js#L91-L92
- https://www.npmjs.com/package/probe-image-size/v/7.5.0
- https://www.vulncheck.com/advisories/probe-image-size-before-7.5.0-memory-exhaustion-via-webp-exif-chunk-length
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134166
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134166"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach20/20probe-image-size: 11.8M downloads a week
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 89 if added to CISA KEV
- Would score about 84 if CISA's SSVC rates exploitation active
- Would score about 49 if advisories confirm default setups are exposed
Impact
Timeline
- CVE published
- First seen by cve.now
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nodeca/probe-image-size · Advisory GHSA-5v8x-rm7w-m4c7 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134166 |
| Record | NVD · CVE-2026-134166 |
| Other links 4 | |
| Patch | GitHub · nodeca/probe-image-size · Commit d91678ea |
| Repository | GitHub · nodeca/probe-image-size · lib/parse_stream/webp.js · L91-L92 |
| Link | npmjs.com · package/probe-image-size/v/7.5.0 |
| Link | vulncheck.com · advisories/probe-image-size-before-7.5.0-memory-exhaustion-via-webp-exif-chunk-length |
Questions about CVE-2026-134166
Is CVE-2026-134166 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-134166?
probe-image-size (npm): before 7.5.0.
Source: cve.now feed data
How do I fix CVE-2026-134166?
Upgrade to a fixed version: 7.5.0.
Source: cve.now feed data
Related
- CVE-2026-134164probe-image-size before 7.5.0 Denial of Service via EXIF Sub-IFD Traversal
- CVE-2026-104861probe-image-size: Quadratic-time Denial of Service in the SVG Parser
- CVE-2026-134163probe-image-size 7.4.0 ReDoS via SVG Doctype Prolog Parser
- CVE-2026-134165probe-image-size before 7.5.0 Memory Exhaustion via AVIF Box Size
- CVE-2026-84375js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
- CVE-2026-73643js-yaml: Exponential parsing time in the flow collections leads to denial of service
No corrections so far. Something wrong on this page? Report an error.