# CVE-2026-44358: Espressif Shared GitHub DangerJS untrusted search path in entrypoint

Source: https://junglewise.ai/threats/cve-2026-44358-espressif-shared-github-dangerjs-untrusted-search-path-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-28. Updated: 2026-05-28  
License: CC BY 4.0 with a link back

CVE-2026-44358 · Severity: high · CVSS 8.2 · Published 2026-05-28

Espressif Shared GitHub DangerJS is a tool used in software development to automate code reviews and pull request feedback. A security flaw allowed external contributors to run unauthorized code within the automated build environment by submitting a malicious pull request. This could allow an attacker to steal security tokens or modify project data, depending on the permissions granted to the automated workflow.

Vendors: [Espressif Systems](https://junglewise.ai/threats/vendors/espressif-systems).

## Quick answers

**Is CVE-2026-44358 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-44358 being exploited in the wild.

**How severe is CVE-2026-44358?** High severity, with a CVSS score of 8.2, published 28 May 2026.

**Which products and versions are affected?** Espressif Systems Shared-Github-Dangerjs <= 1.0.0.

**Is there a fix for CVE-2026-44358?** A patch was published on 2026-05-28: Version 1.0.1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-44358 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-44358?** Check whether you run Espressif Systems Shared-Github-Dangerjs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability stems from an uncontrolled search path (CWE-427) and the inclusion of functionality from an untrusted control sphere (CWE-829) within the action's entrypoint.sh script. When a workflow uses pull_request_target, the action copies the fork's checkout into the workspace and then executes DangerJS using 'npx'. Because 'npx' and Node.js module resolution look in the current working directory, an attacker can provide a malicious binary or 'node_modules' directory in their fork to hijack execution. This allows for arbitrary code execution within the runner container. If the workflow has elevated GITHUB_TOKEN permissions (e.g., pull-requests: write or contents: write), the attacker can exfiltrate secrets or modify the upstream repository. The issue is fixed in version 1.0.1 by using absolute paths for binaries and clearing the workspace node_modules before execution.

## Affected products

- Espressif Systems shared-github-dangerjs <= 1.0.0

## Timeline

- 2026-05-08: advisory: GitHub Security Advisory published by maintainer
- 2026-05-28: disclosed: CVE published to NVD
- 2026-05-28: patched: Version 1.0.1 released

## References

- [https://github.com/espressif/shared-github-dangerjs/commit/d742408028135ea200982b5b2e3e438dc4e5a25d](https://github.com/espressif/shared-github-dangerjs/commit/d742408028135ea200982b5b2e3e438dc4e5a25d)
- [https://github.com/espressif/shared-github-dangerjs/security/advisories/GHSA-wm3p-pv54-6w73](https://github.com/espressif/shared-github-dangerjs/security/advisories/GHSA-wm3p-pv54-6w73)