Live › vulnerability › CVE-2026-97058
Go to dashboardThis advisory is withdrawn: the sprintf-js npm package (through 1.1.3) passes unvalidated precision values to toFixed/toExponential/toPrecision, which throw RangeError. An attacker who controls a format string can make the calling operation throw, which the maintainers say is the application's job to handle.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 5h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| sprintf-js | npm | <= 1.1.3 | – |
npm ls sprintf-js to see whether sprintf-js 1.1.3 or lower is in the dependency treeUnknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
This advisory has been withdrawn because it is the responsibility of an application to handle exceptions appropriately. This link is maintained to preserve external references.
sprintf-js through 1.1.3 passes unbounded precision specifiers to toFixed, toExponential, and toPrecision methods without validation, causing uncaught RangeError exceptions. Attackers who control format strings can inject precision values exceeding ECMAScript limits to abort calling operations with minimal payload.
This page as .md · .json · in your agent: get_signal("CVE-2026-97058")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.