Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

Prototype Pollution in js-data

CVE-2020-28442GHSA-mqgv-67vx-g4m5

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (js-data 3.0.10), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm js-data

    Affected
    < 3.0.10
    Fixed in
    3.0.10

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2020-28442: 1.98% estimated exploitation activity in the next 30 days; percentile 80.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

All versions of package js-data prior to 3.0.10 are vulnerable to Prototype Pollution via the deepFillIn function.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-mqgv-67vx-g4m5

  2. Revision 1 · created ·

    Published from osv record GHSA-mqgv-67vx-g4m5

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-28442

Advisory: Prototype Pollution in js-data
IDs: CVE-2020-28442, GHSA-mqgv-67vx-g4m5
Record: https://patchnext.com/advisories/cve-2020-28442 (revision 2, source checked 26 Oct 2026, 12:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: js-data 3.0.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm js-data: affected < 3.0.10; fixed in 3.0.10

## Suggested inspection (read-only)
- `npm ls js-data --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on js-data.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-mqgv-67vx-g4m5 (OSV record GHSA-mqgv-67vx-g4m5 lists affected ranges: npm js-data >=0 <3.0.10 (fixed))
- Verified: https://github.com/advisories/GHSA-mqgv-67vx-g4m5 (GitHub-reviewed advisory GHSA-mqgv-67vx-g4m5 lists affected ranges: npm js-data >=0 <3.0.10)

Commands are suggestions: review each one before running it.

Loading voting…