Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 28 Oct 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Samverschueren
Samverschueren decode-uri-component |
|
| Vendors & Products |
Samverschueren
Samverschueren decode-uri-component |
Wed, 28 Oct 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | decode-uri-component provides a more robust alternative to decodeURIComponent. Prior to 0.5.1, decodeUriComponent in index.js falls back to customDecodeURIComponent after native decoding throws, and the fallback collects every distinct percent-encoded run before performing a full-string regular-expression replacement for each entry. Malformed input containing many distinct runs can therefore make both the number of replacements and the scanned input length grow together, causing quadratic CPU consumption and blocking the Node.js event loop; request-body inputs can reach the demonstrated size, while ordinary URL header limits reduce the practical delay. This issue is fixed in version 0.5.1. | |
| Title | decode-uri-component: Denial of service via quadratic replacement of percent-encoded runs | |
| Weaknesses | CWE-400 CWE-407 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-28T20:37:19.057Z
Reserved: 2026-10-28T17:25:37.562Z
Link: CVE-2026-118664
No data.
Status : Received
Published: 2026-10-28T21:16:56.687
Modified: 2026-10-28T21:16:56.687
Link: CVE-2026-118664
No data.
OpenCVE Enrichment
Updated: 2026-10-28T22:00:18Z