Skip to main content
Menu
CVEs

probe-image-size memory exhaustion via oversized AVIF box parsing

CVE-2026-134165Published , updated

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 7.5.0
Who is exposed
Not reported

Summary

probe-image-size, a Node.js image-probing library, is affected in versions before 7.5.0. A remote attacker with no login can supply a crafted AVIF image, either as a stream or through a URL, that declares an oversized box, causing the parser to buffer data until memory runs out and the process becomes unavailable.

Written by a model

Original description

probe-image-size before 7.5.0 contains an unbounded memory allocation vulnerability in lib/parse_stream/avif.js that allows remote attackers to exhaust memory via attacker-declared ftyp or meta box sizes. Attackers can supply an AVIF stream or URL to probe(url) or probe(stream) declaring a huge box length, forcing the parser to buffer all received bytes and causing denial of service.

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-134165 (probe-image-size before 7.5.0 Memory Exhaustion via AVIF Box Size), 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-134165 (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-134165 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134165 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-7pqp-3q23-mwr8
- https://github.com/nodeca/probe-image-size/commit/2d37c88f56c2fa3948f383beb16c67c95ef09eee
- https://github.com/nodeca/probe-image-size/blob/64565c3c8b4b69655426cdfce250e6a93455c9da/lib/parse_stream/avif.js#L151
- 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-avif-box-size
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-134165
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-134165"}.

Affected versions

cve.now Index

44Pof 100 · provisional · methodology v3
  • 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

  1. CVE published
  2. First seen by cve.now

Evidence 7

Questions about CVE-2026-134165

Is CVE-2026-134165 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-134165?

probe-image-size (npm): before 7.5.0.

Source: cve.now feed data

How do I fix CVE-2026-134165?

Upgrade to a fixed version: 7.5.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.