You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Published npm-shrinkwrap.json pins npm@11.19.0 with vulnerable tar@7.5.19 #3642
I confirmed the following published CLI releases contain the same vulnerable dependency chain:
@salesforce/cli@2.149.9
@salesforce/cli@2.150.6 (current latest)
@salesforce/cli@2.151.6 (current latest-rc)
Dependency path:
@salesforce/cli
└── npm@11.19.0
└── tar@7.5.19
Consumer impact
Dependabot reports this as a high-severity runtime vulnerability. Consumers cannot cleanly remediate it themselves because the published CLI shrinkwrap dictates the nested npm dependency.
I tested the following approaches:
npm update npm
Root-level npm overrides
Overrides scoped beneath @salesforce/cli
Adding npm@11.19.1 as a direct dependency
Manually updating the consuming repository's package-lock.json
None fixes a clean installation. npm ci follows the CLI's published shrinkwrap and reinstalls npm@11.19.0 and tar@7.5.19. A manual lockfile edit can make dependency scanning appear fixed while leaving the installed package vulnerable.
Requested fix
Please update the CLI's generated shrinkwrap to use npm@11.19.1 or newer and publish a new @salesforce/cli release.
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.
Hello @boveus 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).
A few more things to check:
Make sure you've provided detailed steps to reproduce your issue.
A repository that clearly demonstrates the bug is ideal.
Make sure you've installed the latest version of Salesforce CLI. (docs)
Better yet, try the rc or nightly versions. (docs)
Try running the doctor command to diagnose common issues.
Releases 2.149.9, 2.150.6, and 2.151.6 pin npm@11.19.0
That npm release bundles vulnerable tar@7.5.19
npm@11.19.1 bundles fixed tar@7.5.22
Consumer overrides and lockfile updates cannot supersede the published npm-shrinkwrap.json
Thanks for reporting this @boveus, I've got a bump merged in oclif/plugin-plugins#1394
This will make it into a nightly build of the CLI soon, however, it will not make it into the latest version of the CLI until Sept 30th. We currently have our promotions paused for Dreamforce
Activity
github-actions commentedon Sep 4, 2026
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.
github-actions commentedon Sep 4, 2026
Hello @boveus 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of
version --verbose --jsonfor the CLI you're using (sforsfdx).A few more things to check:
rcornightlyversions. (docs)doctorcommand to diagnose common issues.Thank you!
boveus commentedon Sep 4, 2026
Releases 2.149.9, 2.150.6, and 2.151.6 pin npm@11.19.0
That npm release bundles vulnerable tar@7.5.19
npm@11.19.1 bundles fixed tar@7.5.22
Consumer overrides and lockfile updates cannot supersede the published npm-shrinkwrap.json
git2gus commentedon Sep 8, 2026
This issue has been linked to a new work item: W-24125144
iowillhoit commentedon Sep 8, 2026
Thanks for reporting this @boveus, I've got a bump merged in oclif/plugin-plugins#1394
This will make it into a
nightlybuild of the CLI soon, however, it will not make it into thelatestversion of the CLI until Sept 30th. We currently have our promotions paused for Dreamforceiowillhoit commentedon Oct 13, 2026
Hey @boveus, this is been released in the
latestversion of the cli. Closing this issue