What is CVE-2020-7735?

CVE-2020-7735 is a medium-severity OS command injection vulnerability in ng-packagr (npm), affecting versions < 10.1.1. It is fixed in 10.1.1. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

How severe is CVE-2020-7735?

CVE-2020-7735 has a CVSS score of 6.6 (Medium). 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 ng-packagr are affected by CVE-2020-7735?

ng-packagr (npm) versions < 10.1.1 is affected.

Is there a fix for CVE-2020-7735?

Yes. CVE-2020-7735 is fixed in 10.1.1. Upgrade to this version or later.

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

Whether CVE-2020-7735 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-7735 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-7735 in ng-packagr

Q: How severe is CVE-2020-7735?

CVE-2020-7735 has a CVSS score of 6.6 (Medium). 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 ng-packagr are affected by CVE-2020-7735?

ng-packagr (npm) versions < 10.1.1 is affected.

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

Yes. CVE-2020-7735 is fixed in 10.1.1. Upgrade to this version or later.

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

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

Upgrade ng-packagr to 10.1.1 or later.

Summary

OS Command Injection in ng-packagr

The package ng-packagr before 10.1.1 are vulnerable to Command Injection via the styleIncludePaths option.

Impact

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2020-7735 has a CVSS score of 6.6 (Medium). The vector is network-reachable, high 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 (10.1.1); upgrading removes the vulnerable code path.

Affected versions

ng-packagr (< 10.1.1)

Security releases

ng-packagr → 10.1.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 ng-packagr to 10.1.1 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is CVE-2020-7735? CVE-2020-7735 is a medium-severity OS command injection vulnerability in ng-packagr (npm), affecting versions < 10.1.1. It is fixed in 10.1.1. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
How severe is CVE-2020-7735? CVE-2020-7735 has a CVSS score of 6.6 (Medium). 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 ng-packagr are affected by CVE-2020-7735? ng-packagr (npm) versions < 10.1.1 is affected.
Is there a fix for CVE-2020-7735? Yes. CVE-2020-7735 is fixed in 10.1.1. Upgrade to this version or later.
Is CVE-2020-7735 exploitable, and should I be worried? Whether CVE-2020-7735 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-7735 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-7735? Upgrade ng-packagr to 10.1.1 or later.