PatchTheCVEng-packagr vulnerabilities and fixes
Recent CVEs affecting ng-packagr, with upgrade or downgrade steps. 1 tracked.
Also searched as: ng packagr.
ng-packagr has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2020-09-25. Highest priority: CVE-2020-7735 (score 44/100).
- CVE-2020-7735 MEDIUM 6.6 UPGRADE The package ng-packagr before 10.1.1 are vulnerable to Command Injection via the styleIncludePaths option.
FAQ
How do I fix ng-packagr vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is ng-packagr being exploited right now?
None of the tracked ng-packagr CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which ng-packagr CVE should I patch first?
CVE-2020-7735 currently ranks highest (44/100): The package ng-packagr before 10.1.1 are vulnerable to Command Injection via the styleIncludePaths option..