How severe is GHSA-vcc3-ghjq-m6fr?

No CVSS score has been assigned to GHSA-vcc3-ghjq-m6fr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vcc3-ghjq-m6fr?

GHSA-vcc3-ghjq-m6fr affects the following packages: decode-uri-component (npm). Ecosystems affected: npm.

How do I fix GHSA-vcc3-ghjq-m6fr?

Update decode-uri-component to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vcc3-ghjq-m6fr is resolved across your whole dependency graph.

How do I detect GHSA-vcc3-ghjq-m6fr 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-vcc3-ghjq-m6fr if there is no patch (or I can't update yet)?

Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Is GHSA-vcc3-ghjq-m6fr actively exploited in the wild?

No public exploit code has been indexed for GHSA-vcc3-ghjq-m6fr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-vcc3-ghjq-m6fr?

GHSA-vcc3-ghjq-m6fr has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-vcc3-ghjq-m6fr?

GHSA-vcc3-ghjq-m6fr is classified as Uncontrolled Resource Consumption (CWE-400), CWE-407 (CWE-407). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vcc3-ghjq-m6fr published, and has it been updated?

GHSA-vcc3-ghjq-m6fr was published on August 31, 2026 and was last updated on September 10, 2026. 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

decode-uri-component: Denial of service via exponential decoding of malformed percent-encoded inputGHSA-vcc3-ghjq-m6fr

Fix: SamVerschueren/decode-uri-component@fa479da

GHSA-vcc3-ghjq-m6fr is a Uncontrolled Resource Consumption vulnerability in decode-uri-component. A fix is available for decode-uri-component — see the affected versions and patch details below.

Also known asCVE-2026-45822

Published

Aug 31, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-vcc3-ghjq-m6fr.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

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

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.

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

decode-uri-componentnpm

28.3Mdownloads / week

Description

Impact

An attacker who can supply input to decodeUriComponent() (directly or via a dependency that uses this package on URL/query/path data) can cause excessive CPU usage and application unresponsiveness. This is an availability issue; there is no known memory corruption, data disclosure, or remote code execution impact.

Patches

Upgrade to [email protected].

Workarounds

Limit the size of the input.

Affected Packages

1 total 1 fixed

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

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.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vcc3-ghjq-m6fr is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

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

A denial of service flaw was found in the decode-uri-component npm package. The decode() function exhibits super-linear time complexity when processing input containing many percent-encoded sequences, allowing an attacker to cause significant CPU consumption and event-loop blocking. In Red Hat products where this…

Workaround published by Red Hat

Validate and limit the length of any user-controlled input before passing it to decode-uri-component's decode() function. Inputs containing more than approximately 200 percent-encoded tokens (e.g. '%ab' sequences) can trigger noticeable delays. Reject or truncate URI components exceeding a reasonable length threshold before decoding. A fix exists in the upstream repository (commit fa479daf) but has not yet been included in an npm release.

Source: Red Hat security advisory for GHSA-vcc3-ghjq-m6fr (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Migration Toolkit 1.8	`rhmtc/openshift-migration-ui-rhel8:1783690532`	RHSA-2026:41928
Red Hat Quay 3.10	`quay/quay-rhel8:1783750447`	RHSA-2026:41031
Red Hat Quay 3.12	`quay/quay-rhel8:1783751865`	RHSA-2026:42146
Red Hat Quay 3.12	`quay/quay-rhel8:1784353904`	RHSA-2026:43052
Red Hat Quay 3.15	`quay/quay-rhel8:1785261506`	RHSA-2026:48933
Red Hat Quay 3.16	`quay/quay-rhel9:1783955846`	RHSA-2026:41066
Red Hat Quay 3.9	`quay/quay-rhel8:1784125838`	RHSA-2026:40262
Red Hat Satellite 6.18	`satellite/iop-vulnerability-frontend-rhel9:1785762027`	RHSA-2026:51348

Frequently Asked Questions

### Impact An attacker who can supply input to `decodeUriComponent()` (directly or via a dependency that uses this package on URL/query/path data) can cause excessive CPU usage and application unresponsiveness. This is an availability issue; there is no known memory corruption, data disclosure, or remote code execution impact. ### Patches Upgrade to `[email protected]`. ### Workarounds Limit the size of the input.

O3 Security · Impact-Aware SCA

Is GHSA-vcc3-ghjq-m6fr in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works