Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2020-7735 — ng-packagr

MEDIUMFix: ng-packagr/ng-packagr@bda0fff

CVE-2020-7735 is a medium-severity (CVSS 6.6) OS Command Injection vulnerability in ng-packagr. A fix is available for ng-packagr — see the affected versions and patch details below.

OS Command Injection in ng-packagr

Also known asGHSA-qm28-7hqv-wg5jSNYK-JS-NGPACKAGR-1012427
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk
1.89%2.33%2.77%3.21%2.7%2.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-7735 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

390other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
ng-packagrnpm
1.7Mdownloads / week

Description

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

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmng-packagrall versions10.1.1npm install ng-packagr@10.1.1

Affected Products

1 product · 1 configurations
Application
ng-packagrng-packagr_project
< 10.1.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ng-packagr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update ng-packagr to 10.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7735 is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

The package ng-packagr before 10.1.1 are vulnerable to Command Injection via the styleIncludePaths option.
O3 Security · Impact-Aware SCA

Is CVE-2020-7735 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-7735: ng-packagr — Fixed in 10.1.1