Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/SamVerschueren/decode-uri-component/commit/fad01d65b93bd3f2f0
- https://github.com/SamVerschueren/decode-uri-component/releases/tag/v0.5.1
- https://github.com/SamVerschueren/decode-uri-component/security/advisories/GHSA-
FAQ
What is CVE-2026-118664?
CVE-2026-118664 is a documented vulnerability. 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 t...
How severe is CVE-2026-118664?
CVSS scoring is not yet available for CVE-2026-118664. Check NVD for updates.
Is there a patch for CVE-2026-118664?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.