CVE-2022-0841: OS Command Injection in GitHub repository ljharb/npm-lockfile in v2.0.3 and v2.0.4.

Q: How do I fix CVE-2022-0841?

npm-lockfile: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2022-0841 being exploited?

CVE-2022-0841 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-0841 affect?

CVE-2022-0841 affects npm-lockfile. Severity is critical (CVSS 9.8). OS Command Injection in GitHub repository ljharb/npm-lockfile in v2.0.3 and v2.0.4.

Q: How urgent is CVE-2022-0841?

Priority 65/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2022-0841 is a critical-severity flaw (CVSS 9.8) affecting npm-lockfile. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

OS Command Injection in GitHub repository ljharb/npm-lockfile in v2.0.3 and v2.0.4.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.5% (top 15%)
CISA exploited list	No
Weakness	CWE-78
Published	2022-03-03
Last modified	2026-06-17

Publisher (CNA): huntr.dev · Vendor: npm-lockfile project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-03-03 16:15 UTCPublished CVE record published
2026-06-17 04:21 UTCUpdated Record last modified

npm-lockfile project npm-lockfile DOWNGRADE

Affected: 2.0.3 · 2.0.4

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.3

1. Check installed version

npm ls npm-lockfile

2. No fixed release: DOWNGRADE to a release before 2.0.3

npm view npm-lockfile versions npm install npm-lockfile@"<2.0.3"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-0841?

npm-lockfile: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-0841 being exploited?

CVE-2022-0841 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-0841 affect?

CVE-2022-0841 affects npm-lockfile. Severity is critical (CVSS 9.8). OS Command Injection in GitHub repository ljharb/npm-lockfile in v2.0.3 and v2.0.4.

How urgent is CVE-2022-0841?

Priority 65/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

GitHub vulnerabilities

References

← Back to latest CVEs