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.5%, top 58% 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.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.6MEDIUMmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity66% × 45%
Exploitation1% × 40%
Automatability30% × 15%
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

Published

June 30, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated Jun 30, 2026
Patch available. 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

Vendor Advisories for CVE-2026-45822(10)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatsatellite/iop-vulnerability-frontend-rhel9:17857620272026-08-06redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17859373252026-08-06redhat
redhatquay/quay-rhel8:17852615062026-07-30redhat
redhatquay/quay-rhel8:17843539042026-07-21redhat
redhatrhmtc/openshift-migration-ui-rhel8:17836905322026-07-20redhat
redhatquay/quay-rhel8:17837518652026-07-20redhat
redhatquay/quay-rhel8:17837504472026-07-16redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatquay/quay-rhel8:17841258382026-07-15redhat
redhatdotnet8-0-main-8.0.128-1.1.hum12026-07-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
decode-uri-component—
  • every version up to 0.5.0: fixed in 0.5.0
—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× 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.

Showing the most recent 100 of 165 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-27 13:48 UTCEPSS rescore
  11. 2026-09-26 15:58 UTCEPSS rescore
  12. 2026-09-23 17:53 UTCEPSS rescore
  13. 2026-09-23 07:25 UTCEG score recompute
  14. 2026-09-23 07:25 UTCVendor advisory
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-18 06:52 UTCEG score recompute
  18. 2026-09-18 06:52 UTCVendor advisory
  19. 2026-09-17 19:31 UTCEPSS rescore
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-13 14:28 UTCVendor advisory
  24. 2026-09-12 15:12 UTCEG score recompute
  25. 2026-09-12 15:12 UTCVendor advisory
Show 75 more
  1. 2026-09-12 15:01 UTCEPSS rescore
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 09:37 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 14:38 UTCEG score recompute
  8. 2026-09-06 14:38 UTCVendor advisory
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 18:17 UTCEG score recompute
  15. 2026-08-30 18:17 UTCVendor advisory
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 22:44 UTCEG score recompute
  19. 2026-08-27 22:44 UTCVendor advisory
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 06:21 UTCEG score recompute
  24. 2026-08-25 06:21 UTCVendor advisory
  25. 2026-08-24 07:05 UTCVendor advisory
  26. 2026-08-23 07:51 UTCEG score recompute
  27. 2026-08-23 07:51 UTCVendor advisory
  28. 2026-08-23 00:19 UTCEPSS rescore
  29. 2026-08-22 08:35 UTCEG score recompute
  30. 2026-08-22 08:35 UTCVendor advisory
  31. 2026-08-21 23:49 UTCEPSS rescore
  32. 2026-08-21 05:43 UTCEG score recompute
  33. 2026-08-21 05:43 UTCVendor advisory
  34. 2026-08-20 22:55 UTCEPSS rescore
  35. 2026-08-20 06:29 UTCEG score recompute
  36. 2026-08-20 06:29 UTCVendor advisory
  37. 2026-08-19 17:04 UTCEPSS rescore
  38. 2026-08-19 06:56 UTCEG score recompute
  39. 2026-08-19 06:56 UTCVendor advisory
  40. 2026-08-18 13:48 UTCEPSS rescore
  41. 2026-08-18 07:24 UTCEG score recompute
  42. 2026-08-18 07:24 UTCVendor advisory
  43. 2026-08-17 13:47 UTCEPSS rescore
  44. 2026-08-17 07:34 UTCEG score recompute
  45. 2026-08-17 07:34 UTCVendor advisory
  46. 2026-08-16 14:56 UTCEPSS rescore
  47. 2026-08-16 08:20 UTCEG score recompute
  48. 2026-08-16 08:20 UTCVendor advisory
  49. 2026-08-16 02:14 UTCEPSS rescore
  50. 2026-08-15 09:06 UTCEG score recompute
  51. 2026-08-15 09:06 UTCVendor advisory
  52. 2026-08-15 01:30 UTCEPSS rescore
  53. 2026-08-14 09:51 UTCEG score recompute
  54. 2026-08-14 09:51 UTCVendor advisory
  55. 2026-08-13 22:00 UTCEPSS rescore
  56. 2026-08-13 10:37 UTCEG score recompute
  57. 2026-08-13 10:37 UTCVendor advisory
  58. 2026-08-12 13:51 UTCEPSS rescore
  59. 2026-08-12 11:23 UTCEG score recompute
  60. 2026-08-12 11:23 UTCVendor advisory
  61. 2026-08-11 12:08 UTCEG score recompute
  62. 2026-08-11 12:08 UTCVendor advisory
  63. 2026-08-11 00:00 UTCEPSS rescore
  64. 2026-08-10 12:53 UTCEG score recompute
  65. 2026-08-10 12:53 UTCVendor advisory
  66. 2026-08-09 13:46 UTCEPSS rescore
  67. 2026-08-09 13:39 UTCEG score recompute
  68. 2026-08-09 13:39 UTCVendor advisory
  69. 2026-08-08 16:37 UTCEPSS rescore
  70. 2026-08-08 14:25 UTCEG score recompute
  71. 2026-08-08 14:25 UTCVendor advisory
  72. 2026-08-07 15:11 UTCVendor advisory
  73. 2026-08-06 15:56 UTCEG score recompute
  74. 2026-08-06 15:56 UTCVendor advisory
  75. 2026-08-06 13:47 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Same product

1 shown

npm:decode-uri-component

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 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 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45822?
CVE-2026-45822 has a CVSS base score of 6.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-45822?
A fix for CVE-2026-45822 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45822 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs