Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Regular Expression Denial of Service in papaparseGHSA-qvjc-g5vr-mfgr

HIGHFix: mholt/PapaParse#779

GHSA-qvjc-g5vr-mfgr is a high-severity (CVSS 7.5) CWE-1333 vulnerability in papaparse. 1 public exploit reference exists, so weaponization risk is real. A fix is available for papaparse — see the affected versions and patch details below.

Also known asCVE-2020-36649
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.00%0.63%1.26%1.89%0.4%1.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-qvjc-g5vr-mfgr by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

3Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
papaparsenpm
17.0Mdownloads / week

Description

A vulnerability was found in mholt PapaParse up to 5.1.x. It has been classified as problematic. Affected is an unknown function of the file papaparse.js. The manipulation leads to inefficient regular expression complexity. Upgrading to version 5.2.0 is able to address this issue. The name of the patch is 235a12758cd77266d2e98fd715f53536b34ad621. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-218004.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmpapaparseall versions5.2.0npm install papaparse@5.2.0

Affected Products

1 product · 1 configurations
Application
papaparsepapaparse
≥ 5.1.0 && < 5.2.0
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A vulnerability was found in mholt PapaParse up to 5.1.x. It has been cl…

github.comNVDJan 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for papaparse, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update papaparse to 5.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qvjc-g5vr-mfgr is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Versions of `papaparse` prior to 5.2.0 are vulnerable to Regular Expression Denial of Service (ReDos). The `parse` function contains a malformed regular expression that takes exponentially longer to process non-numerical inputs. This allows attackers to stall systems and lead to Denial of Service. ## Recommendation Upgrade to version 5.2.0 or later.
O3 Security · Impact-Aware SCA

Is GHSA-qvjc-g5vr-mfgr in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Regular Expression Denial of Service in papaparse