npm package report

Is sprintf-js safe?

1 known vulnerability, worst severity MODERATE.

// reach

0 direct dependencies

none carry a known advisory

    31 packages depend on it

    an advisory here reaches each of them

    Create a free accountfor every dependency path, dependent and what to upgrade
    // ai model usage

    Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

    cvss
    0.0
    medium

    severity out of 10

    epss
    0.00%
    low

    chance of exploitation in 30 days, 28th percentile of all CVEs

    xyz score
    not scored

    CyberXYZ composite out of 10

    fig. 01 — GHSA-hp3w-g68c-fv3c, the advisory selected below

    // 1 advisories

    GHSA-hp3w-g68c-fv3c

    MODERATECVE-2026-97058

    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.

    // cvss v4.0 vector

    CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

    Attack vector
    Network
    Attack complexity
    Low
    Attack requirements
    None
    Privileges required
    None
    User interaction
    None
    Confidentiality (vulnerable system)
    None
    Integrity (vulnerable system)
    None
    Availability (vulnerable system)
    Low
    Confidentiality (subsequent systems)
    None
    Integrity (subsequent systems)
    None
    Availability (subsequent systems)
    None

    Checked 2026-10-06 at 02:00 UTC. The most recent advisory here was published 2026-09-24. Updated continuously from NVD, GHSA, OSV and CNA feeds.

    Think a verdict here is wrong? Tell us — we respond within 2 business days.