Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

fastest-json-copy vulnerable to Prototype Pollution

CVE-2022-41714GHSA-p5g9-rjcf-95vj

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

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 fastest-json-copy

    Affected
    <= 1.0.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
  • CVE-2022-41714: 0.73% estimated exploitation activity in the next 30 days; percentile 54.15 (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.

fastest-json-copy version 1.0.1 allows an external attacker to edit or add new properties to an object. This is possible because the application does not correctly validate the incoming JSON keys, thus allowing the proto property to be edited.

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

    Amended from ghsa record GHSA-p5g9-rjcf-95vj

  2. Revision 1 · created ·

    Published from osv record GHSA-p5g9-rjcf-95vj

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-2022-41714

Advisory: fastest-json-copy vulnerable to Prototype Pollution
IDs: CVE-2022-41714, GHSA-p5g9-rjcf-95vj
Record: https://patchnext.com/advisories/cve-2022-41714 (revision 2, source checked 26 Oct 2026, 12:17 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm fastest-json-copy: affected <= 1.0.1

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on fastest-json-copy.
- 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-p5g9-rjcf-95vj (OSV record GHSA-p5g9-rjcf-95vj lists affected ranges: npm fastest-json-copy >=0 <=1.0.1)
- Verified: https://github.com/advisories/GHSA-p5g9-rjcf-95vj (GitHub-reviewed advisory GHSA-p5g9-rjcf-95vj lists affected ranges: npm fastest-json-copy >=0 <=1.0.1)

Commands are suggestions: review each one before running it.

Loading voting…