CVE-2026-44358

Technical summary

The vulnerability stems from improper search path handling in entrypoint.sh. When a pull_request_target workflow processes a fork submission, the action copies the fork's checkout into the caller's workspace before invoking DangerJS. This creates an untrusted search path for both binary resolution (PATH environment variable) and Node.js module resolution (node_modules directories). An attacker-controlled fork can place malicious binaries or Node.js modules in predictable locations that will be discovered and executed in place of the legitimate action code. The issue affects the interaction between workflow context (which allows fork code access) and action execution context (which should run only trusted code). Fixed in version 1.0.1.

Business impact

This vulnerability directly threatens CI/CD pipeline integrity. Malicious pull requests can execute arbitrary code within the action container, potentially allowing attackers to: steal secrets and credentials stored in the workflow environment, compromise build artifacts, inject malicious code into repositories, modify CI/CD configurations, or pivot to downstream systems. Organizations using this action in pull_request_target workflows are at immediate risk, as fork pull requests are a common contribution mechanism. The impact is particularly severe because CI/CD systems often have broad access to source code, deployment credentials, and artifact storage.

Affected systems

Espressif Shared GitHub DangerJS Action versions prior to 1.0.1 are affected. This includes any GitHub Actions workflow that uses the action in a pull_request_target context to process fork contributions. Organizations using this action as a reusable workflow component for automated code review or validation are in scope. The action is specific to Espressif projects but may be used across multiple repositories or forks of Espressif codebases.

Exploitability

Exploitability is high. The vulnerability requires only network access and user interaction (opening a pull request), with no authentication or special privileges needed from the attacker. An attacker can craft a malicious fork with poisoned binaries or Node.js modules and submit a pull request. The pull_request_target workflow event automatically processes the pull request in the action's container, triggering the code execution. No patch installation or special configuration is required to exploit this; the flaw is inherent to how the action processes untrusted fork code.

Remediation

Update Espressif Shared GitHub DangerJS Action to version 1.0.1 or later. Organizations should audit their GitHub Actions workflows to identify all uses of this action, particularly those using pull_request_target events with fork processing enabled. After patching, validate that the action correctly isolates fork-supplied code from its own execution context. Consider implementing additional safeguards such as requiring pull request approval before workflow execution, using separate workflow files for fork processing, or restricting secrets access in pull_request_target workflows.

Patch guidance

Upgrade to version 1.0.1 of the Espressif Shared GitHub DangerJS Action. Update any workflow files that reference this action by changing the version pin to @1.0.1 or later (or @main if you track the default branch). Test the updated action in a non-production workflow first to ensure compatibility. Verify against the official Espressif repository to confirm the patch version and any associated release notes. After applying the patch, re-run recently processed pull requests from forks to ensure they do not contain injected artifacts.

Detection guidance

Review CI/CD logs for the action's execution to identify suspicious binary or module resolution behavior prior to the patch. Look for unexpected file access patterns in the action's working directory, particularly any execution of code from subdirectories created by fork checkouts. Monitor for pull requests from forks that modified entrypoint.sh, package.json, or similar files that could influence code resolution. Examine GitHub Actions run logs for unusual environment variable values (PATH, NODE_PATH) or error messages related to module resolution. If secrets were exfiltrated during a compromised run, rotate all credentials used by the workflow.

Why prioritize this

This vulnerability merits immediate attention due to its high CVSS score (8.2), network-based exploitability, and direct impact on CI/CD security. The attack surface includes any fork contributor, making it broadly exploitable. The consequence—arbitrary code execution in a privileged CI/CD context—can compromise source code integrity, build artifacts, and organizational secrets. Although not yet listed on the CISA KEV catalog, the simplicity of exploitation and severity of impact justify urgent patching.

Risk score, explained

CVSS 3.1 score of 8.2 (HIGH) reflects: network-based attack vector requiring only a fork pull request submission; low attack complexity with no special conditions; no privilege requirement from the attacker; user interaction needed (pull request review/merge, though automated in many workflows); scope change due to impact beyond the action itself (workflow-wide code execution); low confidentiality impact (secrets may be leaked but data exfiltration is secondary); high integrity impact (arbitrary code execution enables malicious modifications); no availability impact.

Frequently asked questions