Vulnerabilities in pkg:npm/probe-image-size
PACKAGECVE-2026-104861 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting probe-image-size libraries in the npm ecosystem. The issue involves quadratic-time denial of service in the svg parser. Remediation is available by upgrading affected packages to version 7.4.0.
pkg:npm/probe-image-size
Vulnerability advisories affecting package pkg:npm/probe-image-size. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-gjj5-9665-rwrc | CVE-2026-104861 | HIGH | probe-image-size: Quadratic-time Denial of Service in the SVG Parser |
CVE-2026-104861 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2026-104861
To remediate this vulnerability, upgrade all affected probe-image-size dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install probe-image-size@7.4.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls probe-image-size
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-104861, inspect your project dependencies using npm:
npm ls probe-image-size
Analyze the terminal output to locate any version of probe-image-size in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.4.0), your application is affected.
Note: The npm ls probe-image-size command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In probe-image-size, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-104861 Affected probe-image-size Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
probe-image-size
|
npm |
< 7.4.0
|
7.4.0
|
References
Frequently Asked Questions
What is CVE-2026-104861?
Which probe-image-size versions are affected?
What version fixes CVE-2026-104861?
Is probe-image-size affected?
What is the CVSS score of CVE-2026-104861?
What CWE is associated with CVE-2026-104861?
How can I check npm dependencies for CVE-2026-104861?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-gjj5-9665-rwrc",
"modified" : "2026-10-02T23:18:02Z",
"published" : "2026-10-02T23:18:02Z",
"aliases" : [ "CVE-2026-104861" ],
"summary" : "probe-image-size: Quadratic-time Denial of Service in the SVG Parser",
"details" : "## Overview\n\n`probe-image-size` scans the SVG header with a searching regular expression, `/<[-_.:a-zA-Z0-9][^>]*>/`. On input that contains many `<` characters but no `>`, the engine restarts the `[^>]*` scan at every `<` position and runs to end of input each time, giving quadratic time complexity.\n\nBoth the synchronous and the streaming parser are affected.\n\n## Impact\n\nEvery entry point that reaches the SVG parser is affected: `probe.sync()`, `probe(stream)` and `probe(url)`. The URL form is the most exposed one — the input is fetched from a remote host, so an attacker only needs to supply a link.\n\nProcessing a crafted buffer blocks the Node.js event loop at 100% CPU for the whole duration. In production environments such as upload validators, image proxies or link unfurl services, a small number of concurrent requests is enough to deny service.\n\n## Root Cause Analysis\n\nTwo independent problems.\n\n1. **Absence of input size cap in the sync path.** `lib/parse_sync/svg.js` copied the entire buffer into a string and matched against it. There was no size limit at all, so cost scaled with the size of the attacker-supplied buffer.\n\n2. **Repeated rescanning in the stream path.** `lib/parse_stream/svg.js` did cap accumulated data at 64 KB, but called `parseSvg(str)` on the whole accumulated string on *every* chunk, giving `O(chunks × N²)`. The cap does not help here: the more chunks the input is split into, the more times the quadratic scan is repeated.\n\n Chunk size is influenced by the sender. `highWaterMark` (16 KB) is a buffering threshold, not a lower bound — a socket read returns whatever has arrived. A server that writes one byte at a time produces one-byte chunks; this was confirmed against the real `needle` pipeline with default options.\n\nThe original report identified (1) only, and stated that the 64 KB cap mitigates the streaming path. It does not.\n\n## Proof of Concept (PoC)\n\nSynchronous:\n\n```js\nconst probe = require('probe-image-size')\n\n// ~200 KB of '<a' — contains '<' but never '>'\nprobe.sync(Buffer.from('<a'.repeat(100000), 'latin1'))\n```\n\nStreaming — the same payload split into chunks, slower per byte than the synchronous form:\n\n```js\nconst { Readable } = require('stream')\nconst probe = require('probe-image-size')\n\nconst payload = Buffer.from('<a'.repeat(32768), 'latin1')\nconst chunks = []\nfor (let i = 0; i < payload.length; i += 4096) chunks.push(payload.subarray(i, i + 4096))\n\nawait probe(Readable.from(chunks))\n```\n\nMeasurements on the maintainer's machine:\n\n| path | input | time |\n| --- | --- | --- |\n| `probe.sync()` | 25 KB | 0.9 s |\n| `probe.sync()` | 50 KB | 5.5 s |\n| `probe.sync()` | 100 KB | 18 s |\n| `probe.sync()` | 200 KB | 54 s |\n| `probe(stream)` | 64 KB, 1 chunk | 1.6 s |\n| `probe(stream)` | 64 KB, 4 chunks | 2.9 s |\n| `probe(stream)` | 64 KB, 16 chunks | 9.6 s |",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "probe-image-size"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "7.4.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 7.3.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/nodeca/probe-image-size/security/advisories/GHSA-gjj5-9665-rwrc"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-104861"
}, {
"type" : "WEB",
"url" : "https://github.com/nodeca/probe-image-size/commit/60cc96ac0b671e79e328213d0a8e831312b09e84"
}, {
"type" : "WEB",
"url" : "https://github.com/nodeca/probe-image-size/commit/9b74656d6f973cc59ea2ab1375c0d88390a402ad"
}, {
"type" : "WEB",
"url" : "https://github.com/nodeca/probe-image-size/commit/c032aefabdecf5cb50548ab9ba175db56353078f"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/nodeca/probe-image-size"
}, {
"type" : "WEB",
"url" : "https://github.com/nodeca/probe-image-size/releases/tag/7.4.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-1333", "CWE-400" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-10-02T23:18:02Z",
"nvd_published_at" : "2026-10-02T18:17:02Z"
}
}