Prototype pollution in total.js

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

EPSS

• CVE-2020-28495: 3.76% estimated exploitation activity in the next 30 days; percentile 89.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

There is a prototype pollution vulnerability in the package total.js before version 3.4.7. The set function can be used to set a value into the object according to the path. However the keys of the path being set are not properly sanitized, leading to a prototype pollution vulnerability. The impact depends on the application. In some cases it is possible to achieve Denial of service (DoS), Remote Code Execution or Property Injection.

Published by the source

5 Feb 2021, 20:43 UTC

Last modified by the source

8 Jul 2026, 06:49 UTC

Source last checked

26 Oct 2026, 12:26 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6cf8-qhqj-vjqm

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6cf8-qhqj-vjqm

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

# Patch Next advisory brief: CVE-2020-28495

Advisory: Prototype pollution in total.js
IDs: CVE-2020-28495, GHSA-6cf8-qhqj-vjqm
Record: https://patchnext.com/advisories/cve-2020-28495 (revision 2, source checked 26 Oct 2026, 12:26 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: total.js 3.4.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm total.js: affected < 3.4.7; fixed in 3.4.7

## Suggested inspection (read-only)
- `npm ls total.js --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 total.js.
- 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-6cf8-qhqj-vjqm (OSV record GHSA-6cf8-qhqj-vjqm lists affected ranges: npm total.js >=0 <3.4.7 (fixed))
- Verified: https://github.com/advisories/GHSA-6cf8-qhqj-vjqm (GitHub-reviewed advisory GHSA-6cf8-qhqj-vjqm lists affected ranges: npm total.js >=0 <3.4.7)

Commands are suggestions: review each one before running it.