Skip to main content
Menu
CVEs

probe-image-size denial of service in EXIF sub-IFD parsing

Affects probe-image-size 7.4.0 and earlier when it parses JPEG images with crafted EXIF sub-IFD tags. Fixed in 7.5.0.

CVE-2026-134164Published , updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 7.5.0
Who is exposed
Not reported

Summary

The probe-image-size package, before version 7.5.0, can be made to consume excessive CPU when it parses a crafted JPEG with self-referencing EXIF data. An attacker can send such a file remotely without logging in, which can freeze the Node.js event loop for roughly 23 seconds.

Written by a model

Original description

probe-image-size before 7.5.0 contains an algorithmic-complexity denial of service vulnerability in lib/exif_utils.js that allows remote unauthenticated attackers to exhaust CPU by supplying self-referencing EXIF IFDs. Attackers can submit a crafted 9.6 KB JPEG with repeated ExifIFD and InteropIFD pointers to block the Node.js event loop for about 23 seconds.

Who should check

Teams running probe-image-size 7.4.0 or earlier in Node.js services that parse uploaded images, unfurl URLs or run image proxies

“probe-image-size 7.4.0 (npm latest, published 2026-08-15)”

github.com

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-134164 (probe-image-size before 7.5.0 Denial of Service via EXIF Sub-IFD Traversal), 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-134164 (entry last updated 2026-11-20):
Affected:
- npm package probe-image-size: fixed in 7.5.0
Fixed versions: 7.5.0.
Conditions (all must be true for the bug to be hit):
- probe-image-size before 7.5.0 (affected versions 7.4.0 and earlier) (source: https://www.vulncheck.com/advisories/probe-image-size-before-7.5.0-denial-of-service-via-exif-sub-ifd-traversal)
- Image has a JPEG APP1 EXIF segment whose IFDs point back at themselves through ExifIFD and InteropIFD tags (source: https://github.com/nodeca/probe-image-size/security/advisories/GHSA-gvwc-5hr5-44p8)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134164 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134164 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-gvwc-5hr5-44p8
- https://github.com/nodeca/probe-image-size/commit/d91678eaff2aad93f7b05bc5212b75856164ec7a
- https://github.com/nodeca/probe-image-size/blob/64565c3c8b4b69655426cdfce250e6a93455c9da/lib/exif_utils.js#L210-L216
- https://www.npmjs.com/package/probe-image-size/v/7.5.0
- https://www.vulncheck.com/advisories/probe-image-size-before-7.5.0-denial-of-service-via-exif-sub-ifd-traversal
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-134164
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-134164"}.

Affected versions

cve.now Index

46Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach20/20probe-image-size: 11.8M downloads a week
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 91 if added to CISA KEV
  • Would score about 86 if CISA's SSVC rates exploitation active
  • Would score about 51 if advisories confirm default setups are exposed

Impact

Timeline

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

Evidence 7

Questions about CVE-2026-134164

Is CVE-2026-134164 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

What does this mean?

A small crafted JPEG whose EXIF IFD tags point back at themselves can make the parser loop, blocking the Node.js event loop for about 23 seconds and stalling other requests in the same process.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134164?

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

Source: cve.now feed data

Am I affected, and how do I check?

Versions of probe-image-size before 7.5.0 (7.4.0 and earlier) are affected. To check a version, run npm ls probe-image-size in the project. The issue involves JPEG APP1 EXIF segments whose ExifIFD and InteropIFD tags point back at themselves.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134164?

Upgrade probe-image-size to 7.5.0 or later, which is the fixed version.

Source: vulncheck.com, github.com

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