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

ReDoS via long string of semicolons in tough-cookieGHSA-qhv9-728r-6jqg

MEDIUMFix: salesforce/tough-cookie@6156272

GHSA-qhv9-728r-6jqg is a medium-severity (CVSS 5.3) Improper Input Validation vulnerability in tough-cookie. A fix is available for tough-cookie — see the affected versions and patch details below.

Also known asCVE-2016-1000232
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk
0.42%1.23%2.04%2.86%0.9%2.4%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-qhv9-728r-6jqg by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 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.

4Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
tough-cookienpm
89.3Mdownloads / week

Description

NodeJS Tough-Cookie version 2.2.2 contains a Regular Expression Parsing vulnerability in HTTP request Cookie Header parsing that can result in Denial of Service. This attack appear to be exploitable via Custom HTTP header passed by client. This vulnerability appears to have been fixed in 2.3.0.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmtough-cookieall versions2.3.0npm install tough-cookie@2.3.0

Affected Products

3 products · 7 configurations
Application
api connectibm
≥ 5.0.7.0 && ≤ 5.0.7.2
1 version
5.0.8.0
Application
openshift container platformredhat
3 versions
3.13.23.3
Application
tough-cookiesalesforce
≥ 0.9.7 && ≤ 2.2.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update tough-cookie to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qhv9-728r-6jqg 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Red Hat OpenShift Container Platform 3.2nodejs-0:0.10.47-2.el7RHSA-2016:2101
Red Hat Software Collections for Red Hat Enterprise Linux 6rh-nodejs4-nodejs-tough-cookie-0:2.3.3-2.el6RHSA-2017:2912

Frequently Asked Questions

Affected versions of `tough-cookie` may be vulnerable to regular expression denial of service when long strings of semicolons exist in the `Set-Cookie` header. ## Recommendation Update to version 2.3.0 or later.
O3 Security · Impact-Aware SCA

Is GHSA-qhv9-728r-6jqg in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
ReDoS via long string of semicolons in tough-cookie