What is CVE-2020-36632?

CVE-2020-36632 is a critical-severity security vulnerability in flat (npm), affecting versions < 1.6.2. It is fixed in 1.6.2, 2.0.2, 3.0.1, 4.0.2, 5.0.1.

How severe is CVE-2020-36632?

CVE-2020-36632 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of flat are affected by CVE-2020-36632?

flat (npm) versions < 1.6.2 is affected.

Is there a fix for CVE-2020-36632?

Yes. CVE-2020-36632 is fixed in 1.6.2, 2.0.2, 3.0.1, 4.0.2, 5.0.1. Upgrade to this version or later.

Is CVE-2020-36632 exploitable, and should I be worried?

Whether CVE-2020-36632 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-2020-36632 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.

CVE-2020-36632 in flat

Q: How severe is CVE-2020-36632?

CVE-2020-36632 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of flat are affected by CVE-2020-36632?

flat (npm) versions < 1.6.2 is affected.

Q: Is there a fix for CVE-2020-36632?

Yes. CVE-2020-36632 is fixed in 1.6.2, 2.0.2, 3.0.1, 4.0.2, 5.0.1. Upgrade to this version or later.

Q: Is CVE-2020-36632 exploitable, and should I be worried?

Whether CVE-2020-36632 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-2020-36632 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-2020-36632?

Upgrade: flat to 1.6.2 or later, flat to 2.0.2 or later, flat to 3.0.1 or later, flat to 4.0.2 or later, flat to 5.0.1 or later.

Summary

flat vulnerable to Prototype Pollution

flat helps flatten/unflatten nested Javascript objects. A vulnerability, which was classified as critical, was found in hughsk flat up to 5.0.0. This affects the function unflatten of the file index.js. The manipulation leads to improperly controlled modification of object prototype attributes ('prototype pollution'). It is possible to initiate the attack remotely. Upgrading to version 5.0.1 can address this issue. The name of the patch is 20ef0ef55dfa028caddaedbcb33efbdb04d18e13. It is recommended to upgrade the affected component. The identifier VDB-216777 was assigned to this vulnerability.

Impact

CVE-2020-36632 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.6.2, 2.0.2, 3.0.1, 4.0.2, 5.0.1); upgrading removes the vulnerable code path.

Affected versions

flat (< 1.6.2) flat (>= 2.0.0, < 2.0.2) flat (= 3.0.0) flat (>= 4.0.0, < 4.0.2) flat (= 5.0.0)

Security releases

flat → 1.6.2 (npm) flat → 2.0.2 (npm) flat → 3.0.1 (npm) flat → 4.0.2 (npm) flat → 5.0.1 (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 the following packages to resolve this vulnerability:

flat to 1.6.2 or later; flat to 2.0.2 or later; flat to 3.0.1 or later; flat to 4.0.2 or later; flat to 5.0.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2020-36632? CVE-2020-36632 is a critical-severity security vulnerability in flat (npm), affecting versions < 1.6.2. It is fixed in 1.6.2, 2.0.2, 3.0.1, 4.0.2, 5.0.1.
How severe is CVE-2020-36632? CVE-2020-36632 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of flat are affected by CVE-2020-36632? flat (npm) versions < 1.6.2 is affected.
Is there a fix for CVE-2020-36632? Yes. CVE-2020-36632 is fixed in 1.6.2, 2.0.2, 3.0.1, 4.0.2, 5.0.1. Upgrade to this version or later.
Is CVE-2020-36632 exploitable, and should I be worried? Whether CVE-2020-36632 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-2020-36632 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-2020-36632?
- Upgrade flat to 1.6.2 or later
- Upgrade flat to 2.0.2 or later
- Upgrade flat to 3.0.1 or later
- Upgrade flat to 4.0.2 or later
- Upgrade flat to 5.0.1 or later