CVE-2017-20165: A vulnerability classified as problematic has been found in debug-js debug up to 3.0.x

Q: How do I fix CVE-2017-20165?

debug: upgrade to 2.6.9, 3.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2017-20165 being exploited?

CVE-2017-20165 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-20165 affect?

CVE-2017-20165 affects debug. Severity is low (CVSS 3.5). A vulnerability classified as problematic has been found in debug-js debug up to 3.0.x. This affects the function useColors of the file src/node.js. The manipulation of the argument str leads to inefficient regular expression complexity. Up

Q: How urgent is CVE-2017-20165?

Priority 33/100. No elevated risk signals yet.

Routine

LOW 3.5UPGRADE

CVE-2017-20165 is a low-severity flaw (CVSS 3.5) affecting debug. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability classified as problematic has been found in debug-js debug up to 3.0.x. This affects the function useColors of the file src/node.js. The manipulation of the argument str leads to inefficient regular expression complexity. Upgrading to version 3.1.0 is able to address this issue. The identifier of the patch is c38a0166c266a679c8de012d4eaccec3f944e685. It is recommended to upgrade the affected component. The identifier VDB-217665 wa

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.5 (Low)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	2.1% (top 18%)
CISA exploited list	No
Weakness	CWE-1333
Published	2023-01-09
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: debug project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-01-09 10:15 UTCPublished CVE record published
2026-06-17 01:15 UTCUpdated Record last modified

debug project debug UPGRADE

Affected: < 2.6.9 · >= 3.0.0 and < 3.1.0

Fixed in: 2.6.9, 3.1.0

Safe to downgrade to: a release before 3.0.0

1. Check installed version

npm ls debug

2. UPGRADE to 2.6.9

npm install debug@">=2.6.9"

3. If no update is available yet, DOWNGRADE to a release before 3.0.0

npm view debug versions npm install debug@"<3.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-20165?

debug: upgrade to 2.6.9, 3.1.0. Exact commands for each OS are on this page.

Is CVE-2017-20165 being exploited?

CVE-2017-20165 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-20165 affect?

CVE-2017-20165 affects debug. Severity is low (CVSS 3.5). A vulnerability classified as problematic has been found in debug-js debug up to 3.0.x. This affects the function useColors of the file src/node.js. The manipulation of the argument str leads to inefficient regular expression complexity. Up

How urgent is CVE-2017-20165?

Priority 33/100. No elevated risk signals yet.

Software pages

Node.js vulnerabilities

Related CVEs

CVE-2024-24798 MEDIUM 4.3 UPGRADE Cross-Site Request Forgery (CSRF) vulnerability in SoniNow Team Debug.This issue affects Debug: from n/a throu

References

← Back to latest CVEs