What is CVE-2026-45822?

CVE-2026-45822 is a medium-severity uncontrolled resource consumption vulnerability in decode-uri-component (npm), affecting versions <= 0.4.2. It is fixed in 0.5.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

Which versions of decode-uri-component are affected by CVE-2026-45822?

decode-uri-component (npm) versions <= 0.4.2 is affected.

Is there a fix for CVE-2026-45822?

Yes. CVE-2026-45822 is fixed in 0.5.0. Upgrade to this version or later.

Is CVE-2026-45822 exploitable, and should I be worried?

Whether CVE-2026-45822 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-45822 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-45822?

Upgrade decode-uri-component to 0.5.0 or later.

CVE-2026-45822 in decode-uri-component

Q: Which versions of decode-uri-component are affected by CVE-2026-45822?

decode-uri-component (npm) versions <= 0.4.2 is affected.

Q: Is there a fix for CVE-2026-45822?

Yes. CVE-2026-45822 is fixed in 0.5.0. Upgrade to this version or later.

Q: Is CVE-2026-45822 exploitable, and should I be worried?

Whether CVE-2026-45822 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-45822 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-45822?

Upgrade decode-uri-component to 0.5.0 or later.

CVE-2026-45822

CVE-2026-45822 is a medium-severity uncontrolled resource consumption vulnerability in decode-uri-component (npm), affecting versions <= 0.4.2. It is fixed in 0.5.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

decode-uri-component: Denial of service via exponential decoding of malformed percent-encoded input

Workarounds

Limit the size of the input.

Impact

An attacker who can supply input to decodeUriComponent() (directly or via a dependency that uses this package on URL/query/path data) can cause excessive CPU usage and application unresponsiveness. This is an availability issue; there is no known memory corruption, data disclosure, or remote code execution impact.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Affected versions

decode-uri-component (<= 0.4.2)

Security releases

decode-uri-component → 0.5.0 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade to [email protected].

Frequently Asked Questions

What is CVE-2026-45822? CVE-2026-45822 is a medium-severity uncontrolled resource consumption vulnerability in decode-uri-component (npm), affecting versions <= 0.4.2. It is fixed in 0.5.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
Which versions of decode-uri-component are affected by CVE-2026-45822? decode-uri-component (npm) versions <= 0.4.2 is affected.
Is there a fix for CVE-2026-45822? Yes. CVE-2026-45822 is fixed in 0.5.0. Upgrade to this version or later.
Is CVE-2026-45822 exploitable, and should I be worried? Whether CVE-2026-45822 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-45822 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-45822? Upgrade decode-uri-component to 0.5.0 or later.