Is source-map-js 1.2.0 vulnerable?

source-map-js 1.2.0, a JavaScript package on npm. All 3 versions we track · npm page

1 vulnerability, 1 high

Upgrade source-map-js from 1.2.0 to 1.2.2 or later.

Known vulnerabilities in source-map-js 1.2.0

  • High CVSS 7.5

    CVE-2026-93749: source-map-js allows event-loop denial of service through indexed source-map section offsets

    GHSA-68fv-2mgg-jv7q · published 18 Sep 2026 · fixed in 1.2.2

How to fix it

With package-lock.json:

npm install source-map-js@1.2.2
# if it is an indirect dependency: npm update source-map-js (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the package's changelog for breaking changes (especially across major versions), update the lockfile with the package manager (never by hand), and run your tests.

Other versions of source-map-js

Newest version we track without known advisories: 1.2.4.

VersionKnown vulnerabilitiesHighest severity
1.2.4 0 None
1.2.2 0 None
1.2.0 (this page) 1 High

Every version of source-map-js →

Licence

source-map-js 1.2.0 declares BSD-3-Clause .

Check your whole project

source-map-js is one package among hundreds in a lockfile. Upload your lockfile, or paste a public GitHub repository, and get every vulnerable package with the version that fixes it. Free, and no account needed.

Get emailed about new advisories for source-map-js (free, no account)

About this data

Vulnerability data: OSV.dev, last checked 22 November 2026. Licence: deps.dev. AIssue checks the versions on this page every day. Severity comes from the advisory's own rating when it has one, else from its CVSS score.