EM-20261029-RK0B
VulnerabilityHigh severity
decode-uri-component Vulnerability (CVE-2026-118664)
CVE-2026-118664
Status
Developing
Since : signals keep joining.
- First Signal
- Oct 28 21:16 UTCC6 NVD CVE API 2.0
- Page Born
- Oct 29 16:41 UTCsecond source joined
- Last Signal
- Oct 29 16:41 UTC6 days before snapshot
- Sources
- 20 official · 2 research, news or crowd
- Open For
- 7 daysso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The address and ID never change. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedOct 28 21:16 UTCC6 NVD published
- Scored: reachedOct 28 21:16 UTCCVSS 8.2 · EPSS 0.3%
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: not yetNot yetNone in sources yet
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- GHSA-qr28-fpjm-wq7f / CVE-2026-118664: decode-uri-component vulnerable to denial of service via quadratic replacement of percent-encoded runs (opens source in a new tab) npm:decode-uri-component High severityDatabaseC26 GitHub Advisory Database
- CVE-2026-118664 (CVSS 8.2) (opens source in a new tab) 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… High severityDatabaseC6 NVD CVE API 2.0