CVE-2026-48995: pnpm: Tarball hash of GitHub git dependencies is not stored in lockfile
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. Special conditions such as timing or configuration are required.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: pnpm pnpm 10.33.4.
Low priority for now. Upgrade to pnpm pnpm 10.33.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
pnpm is a package manager. Prior to 10.33.4 and 11.0.7, a malicious codeload.github.com server can serve whatever tarball it wants and pnpm will install it regardless of the lockfile. The lockfile does not store the hash of the dependencies from https://codeload.github.com. This means that if this server was compromised or a person's machine configuration was compromised, pnpm would download and install these dependencies. This vulnerability is fixed in 10.33.4 and 11.0.7.
- Published
- Jun 25, 2026
- Updated
- Jun 29, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-353
Report tools
Action score
19
Monitor
Low priority for now.
- CVSS
- 19 / 40 · 4.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 4.8
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pnpm | pnpm | cpe:2.3:a:pnpm:pnpm |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- pnpm pnpmbefore 10.33.4
- pnpm pnpm11.0.0 and later · before 11.0.7
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
pnpm pnpm
- < 10.33.4, >= 11.0.0, < 11.0.7affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | pnpm | from 11.0.0 · before 11.0.7 | 11.0.7 |
| npm | pnpm | before 10.33.4 | 10.33.4 |
Same product
pnpm: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-69264pnpm v10+ Bypass "Dependency lifecycle scripts execution disabled by default"39Monitor
- CVE-2023-37478pnpm incorrectly parses tar archives relative to specification39Monitor
- CVE-2026-55698pnpm: Project env lockfile can short-circuit package-manager resolution and execute lockfile-selected pnpm bytes35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-24056Jan 26, 2026 · pnpm has symlink traversal in file:/git dependencies26Monitor
- ← EarlierCVE-2026-24131Jan 26, 2026 · pnpm has Path Traversal via arbitrary file permission modification26Monitor
- Later →CVE-2026-50014Jun 25, 2026 · pnpm: Git Fetch Argument Injection via Lockfile resolution.commit29Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| pnpm pnpm | 10.33.4 · description | Vendor (CNA) |
| npm:pnpm | 10.33.4 | Package registry (OSV) |
| npm:pnpm | 11.0.7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-353 · Missing Support for Integrity CheckCVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Content Spoofing Via Application API ManipulationCAPEC-389Low
- Manipulating Opaque Client-based Data TokensCAPEC-39likelihood: High · Medium
- Exploitation of Thunderbolt Protection FlawsCAPEC-665likelihood: Low · Very High
- Manipulating StateCAPEC-74likelihood: Medium · High
- Manipulating Writeable Configuration FilesCAPEC-75likelihood: High · Very High
ATT&CK techniques
- Exploitation for Defensive EvasionT1211
- Pre-OS Boot: Component FirmwareT1542.002
- Modify Authentication ProcessT1556
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →