Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Regular Expression Denial of Service in parsejson

CVE-2017-16113GHSA-q75g-2496-mxpp

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 parsejson

    Affected
    <= 0.0.3
    Fixed in
    no fixed version recorded

Sources

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

Affected versions of parsejson are vulnerable to a regular expression denial of service when parsing untrusted user input. Recommendation The parsejson package has not been functionally updated since it was initially released. Additionally, it provides functionality which is natively included in Node.js, and therefore the native JSON.parse() should be used, for both performance and security reasons.

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

    Amended from ghsa record GHSA-q75g-2496-mxpp

  2. Revision 1 · created ·

    Published from osv record GHSA-q75g-2496-mxpp

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-2017-16113

Advisory: Regular Expression Denial of Service in parsejson
IDs: CVE-2017-16113, GHSA-q75g-2496-mxpp
Record: https://patchnext.com/advisories/cve-2017-16113 (revision 2, source checked 26 Oct 2026, 12:08 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 response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm parsejson: affected <= 0.0.3

## Suggested inspection (read-only)
- `npm ls parsejson --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 parsejson.
- 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-q75g-2496-mxpp (OSV record GHSA-q75g-2496-mxpp lists affected ranges: npm parsejson >=0 <=0.0.3)
- Verified: https://github.com/advisories/GHSA-q75g-2496-mxpp (GitHub-reviewed advisory GHSA-q75g-2496-mxpp lists affected ranges: npm parsejson >=0 <=0.0.3)

Commands are suggestions: review each one before running it.

Loading voting…