What is the CVSS score of CVE-2026-44358?

CVE-2026-44358 has a CVSS 3.1 base score of 8.2 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of Espressif shared-github-dangerjs are affected by CVE-2026-44358?

Espressif's shared-github-dangerjs GitHub Action (versions prior to 1.0.1) contains an untrusted search path vulnerability enabling arbitrary code execution within CI/CD pipeline containers during…. A patch is available.

How to fix or mitigate CVE-2026-44358?

Within 24 hours: audit all GitHub workflows using shared-github-dangerjs and enumerate affected repositories; immediately discontinue use of the action or restrict pull_request_target workflows to run only on commits from protected branches (disable for pull_request events from forks). Within 7 days: evaluate alternative security tools for dependency checking (Dependabot, Snyk, or equivalent) and implement job-level GITHUB_TOKEN permissions (permissions.contents: read, permissions.pull-requests: read) to limit attack surface on remaining workflows. Within 30 days: complete migration to patched or alternative tools and formally document approved CI/CD tools in security policy; subscribe to Espressif's advisory channel for version 1.0.1 or later release notification.

Espressif shared-github-dangerjs CVE-2026-44358

EUVD-2026-32908 HIGH

Uncontrolled Search Path Element (CWE-427)

2026-05-28 GitHub_M

Node.js Information Disclosure

8.2

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.2 HIGH

AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

High

Availability

None

Lifecycle Timeline

Patch available

May 28, 2026 - 17:01 EUVD

Source Code Evidence Fetched

May 28, 2026 - 15:52 vuln.today

Analysis Generated

May 28, 2026 - 15:52 vuln.today

DescriptionGitHub Advisory

Espressif Shared GitHub DangerJS is a reusable GitHub Action CI DangerJS workflow for Espressif GitHub projects. Prior to 1.0.1, the action's entrypoint.sh invoked DangerJS from the caller's workspace after copying the fork's checkout into it, creating an untrusted search path for both binary resolution and Node.js module resolution. A fork pull request processed by a pull_request_target workflow could therefore cause fork-supplied code to execute inside the action container in place of the action's own code. This vulnerability is fixed in 1.0.1.

AnalysisAI

Untrusted search path in Espressif's shared-github-dangerjs GitHub Action prior to 1.0.1 allows a fork pull request, when processed by a pull_request_target workflow, to substitute attacker-controlled binaries and Node.js modules for the action's own code. Exploitation yields code execution inside the action container with access to repository secrets and write-scoped GITHUB_TOKEN, with no public exploit identified at time of analysis.

Technical ContextAI

The vulnerability is a CWE-427 (Uncontrolled Search Path Element) flaw in entrypoint.sh of the reusable Espressif DangerJS GitHub Action (CPE cpe:2.3:a:espressif:shared-github-dangerjs). The action ran npx danger ci from the caller's workspace after the fork's checkout had been copied into it; because npx resolves binaries relative to the current working directory's node_modules/.bin and Node.js resolves modules from the nearest node_modules tree, a fork PR could supply both a malicious danger binary and arbitrary modules that Node would load in preference to the action's intended code. The danger here is amplified by the pull_request_target trigger, which runs with the base repository's secrets and a privileged GITHUB_TOKEN, unlike the safer pull_request trigger.

RemediationAI

Vendor-released patch: 1.0.1, which invokes danger via the absolute path /node_modules/.bin/danger and runs rm -rf /github/workspace/node_modules before execution to neutralize fork-supplied modules; upgrade by bumping the uses: reference in calling workflows to espressif/shared-github-dangerjs@1.0.1 (or, preferably, pin to the fix commit SHA d7424080) per the advisory at https://github.com/espressif/shared-github-dangerjs/security/advisories/GHSA-wm3p-pv54-6w73. If immediate upgrade is not possible, switch the calling workflow's trigger from pull_request_target to pull_request so secrets and write-scoped tokens are not exposed to fork code (trade-off: the workflow will no longer be able to post Danger comments back to the PR), or gate the job behind an if: github.event.pull_request.head.repo.full_name == github.repository check to skip fork PRs entirely (trade-off: forks receive no Danger feedback). Avoid relying on permissions: read-all alone, since the underlying hijack still executes attacker code in the runner.