Vulnerability in decode-uri-component (CVE-2026-45822)
Summary
Vulnerability in decode-uri-component (CVE-2026-45822). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.5.0 or later.
Original description
The description as published by the source.
decode-uri-component through 0.4.1 is vulnerable to denial of service. The decode() function splits input on '%' producing N tokens and calls decodeComponents(), exhibiting super-linear parsing time: 200 '%ab' tokens takes approximately 0.7s, 700 tokens approximately 6s, and 1400 tokens approximately 33s. An attacker can cause significant CPU consumption and event-loop blocking via crafted input.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45822 has been found in decode-uri-component.
Risk of unauthorized operations or information disclosure.
What to do: upgrade decode-uri-component to 0.5.0 or later.
If unsure, ask your IT team or search "decode-uri-component CVE-2026-45822" on the vendor's site.
CVE-2026-45822 (decode-uri-component) — CWE-400
Patched: 0.5.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in decode-uri-component.
Check the vendor advisory for the affected versions of decode-uri-component.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.5.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'decode-uri-component' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'decode-uri-component' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
decode-uri-componentを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade decode-uri-component to 0.5.0ステージング環境で 0.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-45822 node-source-map-resolve
References
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com
- web npmjs.com
- web github.com
- web github.com
- web github.com