Command execution via unsanitized peer-dependency names
Published Jul 8, 2026 · Updated Jul 8, 2026
OS command injection in check-peer-dependencies 4.3.0 through 4.3.4 allows context-dependent attackers to execute commands via a crafted project. The solution and installation paths concatenate peer-dependency names from package.json into npm or yarn command strings that shelljs.exec passes to the operating-system shell without neutralizing metacharacters. Execution requires the tool to process an attacker-controlled project with --findSolutions or --install enabled, and injected commands run with the invoking user's privileges.
Summary
What happened
OS command injection in check-peer-dependencies 4.3.0 through 4.3.4 allows context-dependent attackers to execute commands via a crafted project. The solution and installation paths concatenate peer-dependency names from package.json into npm or yarn command strings that shelljs.exec passes to the operating-system shell without neutralizing metacharacters. Execution requires the tool to process an attacker-controlled project with --findSolutions or --install enabled, and injected commands run with the invoking user's privileges.
The record
- CVE
- CVE-2026-15033
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- Chris Thielen
- Product
- check-peer-dependencies
- Classifications
- CWE-77, CWE-78, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.3.0
- Affected versionversion=4.3.1
- Affected versionversion=4.3.2
- Affected versionversion=4.3.3
- Affected versionversion=4.3.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream issue 74 command-injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo