Vulnerability in Espressif Shared GitHub DangerJS (CVE-2026-44358)
Summary
Vulnerability in Espressif Shared GitHub DangerJS (CVE-2026-44358). Data can be tampered with by attackers. Mitigation: upgrade to 1.0.1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44358 has been found in Espressif Shared GitHub DangerJS.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: upgrade Espressif Shared GitHub DangerJS to 1.0.1 or later.
If unsure, ask your IT team or search "Espressif Shared GitHub DangerJS CVE-2026-44358" on the vendor's site.
CVE-2026-44358 (Espressif Shared GitHub DangerJS) — CWE-427 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.0.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-427) exists in Espressif Shared GitHub DangerJS.
Check the vendor advisory for the affected versions of Espressif Shared GitHub DangerJS.
Severity: High (CVSS 8.2/10). Data can be tampered with by attackers.
Update to 1.0.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Espressif Shared GitHub DangerJS を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Espressif Shared GitHub DangerJS to 1.0.1ステージング環境で 1.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com