Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Prototype pollution in JointJS

CVE-2020-28480GHSA-qwp9-52h8-xgg8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (jointjs 3.3.0), 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 jointjs

    Affected
    < 3.3.0
    Fixed in
    3.3.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2020-28480: 1.38% estimated exploitation activity in the next 30 days; percentile 72.07 (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.

The package jointjs before 3.3.0 are vulnerable to Prototype Pollution via util.setByPath (https://resources.jointjs.com/docs/jointjs/v3.2/joint.htmlutil.setByPath). The path used the access the object's key and set the value is not properly sanitized, leading to a Prototype Pollution.

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

    Amended from ghsa record GHSA-qwp9-52h8-xgg8

  2. Revision 1 · created ·

    Published from osv record GHSA-qwp9-52h8-xgg8

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-28480

Advisory: Prototype pollution in JointJS
IDs: CVE-2020-28480, GHSA-qwp9-52h8-xgg8
Record: https://patchnext.com/advisories/cve-2020-28480 (revision 2, source checked 26 Oct 2026, 12:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: jointjs 3.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm jointjs: affected < 3.3.0; fixed in 3.3.0

## Suggested inspection (read-only)
- `npm ls jointjs --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 jointjs.
- 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-qwp9-52h8-xgg8 (OSV record GHSA-qwp9-52h8-xgg8 lists affected ranges: npm jointjs >=0 <3.3.0 (fixed))
- Verified: https://github.com/advisories/GHSA-qwp9-52h8-xgg8 (GitHub-reviewed advisory GHSA-qwp9-52h8-xgg8 lists affected ranges: npm jointjs >=0 <3.3.0)

Commands are suggestions: review each one before running it.

Loading voting…