Description
probe-image-size gets image dimensions without downloading the entire file. Prior to 7.4.0, lib/parse_sync/svg.js and lib/parse_stream/svg.js use the searching regular expression /<[-_.:a-zA-Z0-9][^>]*>/, which repeatedly scans to the end of input when attacker-controlled data contains many less-than characters without a closing greater-than character. The synchronous parser converts and scans the full supplied buffer without an input cap, while the streaming parser reparses the complete accumulated SVG prefix for every received chunk. The probe.sync(), probe(stream), and probe(url) entry points can therefore block the Node.js event loop at full CPU, and attacker-controlled chunking can amplify the streaming cost. This issue is fixed in version 7.4.0.
References6
- github.com/nodeca/probe-image-size/commit/60cc96ac0b671e79e3282…
- github.com/nodeca/probe-image-size/commit/9b74656d6f973cc59ea2a…
- github.com/nodeca/probe-image-size/commit/c032aefabdecf5cb50548…
- github.com/nodeca/probe-image-size/releases/tag/7.4.0
- github.com/nodeca/probe-image-size/security/advisories/GHSA-gjj…
- github.com/nodeca/probe-image-size/security/advisories/GHSA-gjj…
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 37 · as of 10 November 2026
- CWE
- CWE-400CWE-1333
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.