How severe is GHSA-w573-4hg7-7wgq?

GHSA-w573-4hg7-7wgq has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-w573-4hg7-7wgq?

GHSA-w573-4hg7-7wgq affects the following packages: decode-uri-component (npm). Ecosystems affected: npm.

How do I fix GHSA-w573-4hg7-7wgq?

Update decode-uri-component to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w573-4hg7-7wgq is resolved across your whole dependency graph.

How do I detect GHSA-w573-4hg7-7wgq in my npm dependencies?

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

How do I mitigate GHSA-w573-4hg7-7wgq if there is no patch (or I can't update yet)?

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.

Is GHSA-w573-4hg7-7wgq actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-w573-4hg7-7wgq, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-w573-4hg7-7wgq?

GHSA-w573-4hg7-7wgq has an EPSS (Exploit Prediction Scoring System) score of 23.8%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-w573-4hg7-7wgq?

GHSA-w573-4hg7-7wgq is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w573-4hg7-7wgq published, and has it been updated?

GHSA-w573-4hg7-7wgq was published on November 28, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

decode-uri-component vulnerable to Denial of Service (DoS)GHSA-w573-4hg7-7wgq

HIGHFix: SamVerschueren/decode-uri-component@746ca5d

GHSA-w573-4hg7-7wgq is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in decode-uri-component. 2 public exploit references exist, so weaponization risk is real. A fix is available for decode-uri-component — see the affected versions and patch details below.

Also known asCVE-2022-38900

Published

Nov 28, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-w573-4hg7-7wgq.

EPSS Exploitation Probability

via FIRST.org ↗

23.8%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-w573-4hg7-7wgq 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–50% 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.

866other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

decode-uri-componentnpm

17.0Mdownloads / week

Description

decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`decode-uri-component`	all versions	0.2.1`npm install decode-uri-component@0.2.1`

Affected Products

1 product · 1 configurations

Application

decode-uri-componentdecode-uri-component_project

1 version

0.2.0

Exploits & PoCs

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

decode-uri-component 0.2.0 is vulnerable to Improper Input Validation re…

github.comNVDDec 2022

decode-uri-component 0.2.0 is vulnerable to Improper Input Validation re…

github.comNVDDec 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for decode-uri-component, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update decode-uri-component to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w573-4hg7-7wgq is resolved across your whole dependency graph.
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 HatImportant

For OpenShift Container Platform (OCP), Advanced Clusters Management for Kubernetes (ACM) and Advanced Cluster Security (ACS), the NPM decode-uri-component package is only present in source repositories as a development dependency, it is not used in production. Therefore this vulnerability is rated Low for OCP and…

Product	Fixed in	Advisory
Red Hat Enterprise Linux 8	`nodejs:14-8070020230306170042.bd1311ed`	RHSA-2023:1743
Red Hat Enterprise Linux 8.4 Extended Update Support	`nodejs:14-8040020230306170312.522a0ee4`	RHSA-2023:1533
Red Hat Enterprise Linux 8.6 Extended Update Support	`nodejs:14-8060020230306170237.ad008a3a`	RHSA-2023:1742
Red Hat Enterprise Linux 9	`pcs-0:0.11.6-3.el9`	RHSA-2023:6316
Red Hat Migration Toolkit for Containers 1.7	`rhmtc/openshift-migration-ui-rhel8:v1.7.8-5`	RHSA-2023:1428
Red Hat Software Collections for Red Hat Enterprise Linux 7	`rh-nodejs14-0:3.6-2.el7`	RHSA-2023:1744
RHODF-4.13-RHEL-9	`odf4/odf-console-rhel9:v4.13.0-85`	RHSA-2023:3742
RHPAM 7.13.4 async	`decode-uri-component`	RHSA-2023:4983

Frequently Asked Questions

decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.

O3 Security · Impact-Aware SCA

Is GHSA-w573-4hg7-7wgq in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CWE Classification

CWE-20Improper Input Validation

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Nov 28, 2022

First exploit

Dec 1, 2022

3 days after disclosure — rapid exploitation

Last updated

Nov 8, 2023

Identifiers

GHSA-w573-4hg7-7wgq

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Webgithub.com Webgithub.com Weblists.fedoraproject.org Weblists.fedoraproject.org Weblists.fedoraproject.org Weblists.fedoraproject.org Weblists.fedoraproject.org Packagegithub.com

Related vulnerabilities

Also affects decode-uri-component

This CVE is high severity; 1 of 2 other CVEs affecting decode-uri-component is rated as high or higher (top: high).

CVE-2026-45822CVE-2022-38900

Same weakness: CWE-20

This CVE is high severity — higher than any of the other 6 CVEs with CWE-20 (highest there: moderate).

CVE-2026-115883GHSA-85x2-q946-cp5hGHSA-8c8m-p3m8-cjg8GHSA-m943-m63m-w62wCVE-2026-110180CVE-2026-113786Browse all CWE-20

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedNov 8, 2023

decode-uri-component vulnerable to Denial of Service (DoS)GHSA-w573-4hg7-7wgq

Exploitation Status

Proof-of-concept exploit code exists

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is GHSA-w573-4hg7-7wgq in your dependencies?