CVE-2023-37478
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedpnpm is a package manager. It is possible to construct a tarball that, when installed via npm or parsed by the registry is safe, but when installed via pnpm is malicious, due to how pnpm parses tar archives. This can result in a package that appears safe on the npm registry or when installed via npm being replaced with a compromised or malicious version when installed via pnpm. This issue has been patched in version(s) 7.33.4 and 8.6.8.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencepnpm has a vulnerability in its tar archive parser that allows specially crafted tarballs to appear benign when inspected via npm or a registry but execute malicious behavior when installed through pnpm. This enables package substitution attacks where a legitimate package can be replaced with a compromised version at install time.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.33.4>= 8.0.0, < 8.6.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed pnpm versionRun `pnpm --version` in the terminal to obtain the exact version number of pnpm currently in useAffected if The version returned is less than 7.33.4, or is 8.0.0 through 8.6.7 inclusive
-
Verify package source integrityInspect your project dependencies in package.json and lockfile (pnpm-lock.yaml) to confirm all packages come from trusted sourcesAffected if Packages are resolved from untrusted or unofficial registries, or dependency integrity checks are disabled
You are affected if your installed pnpm version falls within the vulnerable ranges (< 7.33.4 or >= 8.0.0 to < 8.6.8) and you install tarballs from external or untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.33.48.6.8
Upgrade pnpm to version 7.33.4, 8.6.8, or later to patch the tarball parsing vulnerability.
Upgrade to pnpm 7.33.4 (for 7.x users) or 8.6.8 (for 8.x users)
- Check current pnpm version by running: pnpm --version
- Determine which major version line you are currently on (7.x or 8.x)
- If on version 7.x, upgrade to 7.33.4 using: npm install -g [email protected]
- If on version 8.x, upgrade to 8.6.8 using: npm install -g [email protected]
- Alternatively, if using corepack, run: corepack prepare [email protected] --activate (or [email protected] for 8.x)
- Verify the upgrade was successful by running: pnpm --version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37478 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-37478 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data