CVE-2026-45822

MEDIUMPre-NVD 6.66.6—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.6
EG Score
6.6(medium)
EPSS
22.3%
KEV
Not listed

Published

June 30, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated Jun 30, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit fa479dafeede (SamVerschueren/decode-uri-component)

Fix landed in SamVerschueren/decode-uri-component commit fa479dafeede — awaiting tagged release

https://github.com/SamVerschueren/decode-uri-component/commit/fa479dafeede7bedf04e5c89aa78f2a78c664005
generic

decode-uri-component/index.js at 00662938dc7c6241547ae8abce7785cc13ffd3f6 · SamVerschueren/decode-uri-component · GitHub

https://github.com/SamVerschueren/decode-uri-component/blob/00662938dc7c6241547ae8abce7785cc13ffd3f6/index.js

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 02:28 UTCEG score recompute
  3. 2026-07-10 03:13 UTCEG score recompute
  4. 2026-07-09 19:10 UTCEPSS rescore
  5. 2026-07-09 03:56 UTCEG score recompute
  6. 2026-07-08 15:16 UTCEPSS rescore
  7. 2026-07-08 04:42 UTCEG score recompute
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-07 05:26 UTCEG score recompute
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 06:11 UTCEG score recompute
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-05 06:53 UTCEG score recompute
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 07:36 UTCEG score recompute
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-03 08:19 UTCEG score recompute
  18. 2026-07-02 09:04 UTCEG score recompute
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 09:47 UTCEG score recompute
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 10:32 UTCEG score recompute
  23. 2026-06-30 10:31 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-45822?
CVE-2026-45822 is a medium vulnerability published on June 30, 2026. 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…
When was CVE-2026-45822 disclosed?
CVE-2026-45822 was first published in the National Vulnerability Database on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45822 actively exploited?
CVE-2026-45822 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45822?
CVE-2026-45822 has a CVSS v3 base score of 6.6 (NVD).
How do I remediate CVE-2026-45822?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45822, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-45822

Explore →

Is Your Infrastructure Affected by CVE-2026-45822?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs