CI code execution via untrusted module search
Published May 28, 2026 · Updated May 28, 2026
Code execution in Espressif Shared GitHub DangerJS before 1.0.1 allows remote attackers to run fork-supplied code in CI containers. The entrypoint copies the fork checkout into the caller workspace, then uses npx and Node.js resolution paths that accept attacker-controlled binaries and modules. Exploitation requires a fork pull request handled by pull_request_target; resulting code inherits the workflow's declared token permissions and exposed secrets.
Summary
What happened
Code execution in Espressif Shared GitHub DangerJS before 1.0.1 allows remote attackers to run fork-supplied code in CI containers. The entrypoint copies the fork checkout into the caller workspace, then uses npx and Node.js resolution paths that accept attacker-controlled binaries and modules. Exploitation requires a fork pull request handled by pull_request_target; resulting code inherits the workflow's declared token permissions and exposed secrets.
The record
- CVE
- CVE-2026-44358
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- Espressif Systems
- Product
- Espressif Shared GitHub DangerJS
- Classifications
- CWE-829, CWE-427, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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=< 1.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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