CVE-2020-36830: A vulnerability was found in nescalante urlregex up to 0.5.0 and classified as problematic

Q: How do I fix CVE-2020-36830?

urlregex: upgrade to 0.5.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-36830 being exploited?

CVE-2020-36830 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-2020-36830 affect?

CVE-2020-36830 affects urlregex. Severity is medium (CVSS 4.3). A vulnerability was found in nescalante urlregex up to 0.5.0 and classified as problematic. This issue affects some unknown processing of the file index.js of the component Backtracking. The manipulation leads to inefficient regular express

Q: How urgent is CVE-2020-36830?

Priority 34/100. Public exploit reference

Routine

MEDIUM 4.3UPGRADE

CVE-2020-36830 is a medium-severity flaw (CVSS 4.3) affecting urlregex. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was found in nescalante urlregex up to 0.5.0 and classified as problematic. This issue affects some unknown processing of the file index.js of the component Backtracking. The manipulation leads to inefficient regular expression complexity. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 0.5.1 is able to address this issue. The identifier of the patch is e5a08

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.8% (top 43%)
CISA exploited list	No
Weakness	CWE-1333
Published	2024-09-02
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: nescalante

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

Am I affected?

Timeline

2024-09-02 18:15 UTCPublished CVE record published
2026-06-17 03:16 UTCUpdated Record last modified

nescalante urlregex UPGRADE

Affected: < 0.5.1

Fixed in: 0.5.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy urlregex || rpm -q urlregex || urlregex --version

2. UPGRADE to 0.5.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade urlregex

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade urlregex

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2020-36830?

urlregex: upgrade to 0.5.1. Exact commands for each OS are on this page.

Is CVE-2020-36830 being exploited?

CVE-2020-36830 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-2020-36830 affect?

CVE-2020-36830 affects urlregex. Severity is medium (CVSS 4.3). A vulnerability was found in nescalante urlregex up to 0.5.0 and classified as problematic. This issue affects some unknown processing of the file index.js of the component Backtracking. The manipulation leads to inefficient regular express

How urgent is CVE-2020-36830?

Priority 34/100. Public exploit reference

References

← Back to latest CVEs