Meshtastic GitHub repo vulnerable to Arbitrary Code Execution via pull_request_target Fork Checkout in CI Workflow
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-829.
Summary
Meshtastic is an open source mesh networking solution. Prior to version 2.7.21.1370b23, the Meshtastic GitHub repository's main_matrix.yml workflow is triggered by pull_request_target and multiple jobs check out the attacker's fork code and execute it with access to repository secrets and elevated GITHUB_TOKEN permissions. No approval gate exists. Pull requests from external users with author_association: "NONE" triggered the CI workflow automatically. The workflow directly executes attacker-controlled files from the fork checkout. This issue could have resulted in supply chain compromise, self-hosted runner compromise, and/or repository takeover for the repo. This issue is separate from GHSA-6mwm-v2vv-pp96, which addressed a command injection via github.head_ref in the setup job of the same workflow. That fix correctly moved to environment variables. However, the more critical fork checkout vulnerability across the check, build, and build-debian-src jobs was not addressed. Version 2.7.21.1370b23 contains a patch for thie issue.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| meshtastic | firmware | before 2.7.21.1370b23 | 2.7.21.1370b23 | Patch available | CNA |
- firmware Vendormeshtastic Affected before 2.7.21.1370b23 Fixed in 2.7.21.1370b23 Patch available CNA
CPE names Threatist (inferred) · 1
Inferred from how NVD named this product before; not given by a source.
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:o:meshtastic:meshtastic_firmware:*:*:*:*:*:*:*:* | — | — | meshtastic |
- cpe:2.3:o:meshtastic:meshtastic_firmware:*:*:*:*:*:*:*:* Versions — — ·meshtastic
Remediation
- Fix · CNA firmware (meshtastic) Fixed in 2.7.21.1370b23
Timeline
- 2026-10-02 Threatist record created from CVE-2026-44359
References
Other 4
- https://github.com/meshtastic/firmware/security/advisories/GHSA-mjx5-98jq-q736
- https://github.com/meshtastic/firmware/security/advisories/GHSA-6mwm-v2vv-pp96
- https://github.com/meshtastic/firmware/commit/5716aeba3bc1e1d34fba9567ff88917ede4a78a5
- https://drive.google.com/file/d/1GdHT2s5hMYCiHt4zrWt1q58mvL7WQC0M/view?usp=sharing
More meshtastic vulnerabilities
- TI-2025-34949 Meshtastic allows crafting of specific NodeInfo packets that overwrite any publicKey saved in the NodeDB CVSS 3.1CRITICAL 9.8
- TI-2025-34948 In Meshtastic, an attacker can spoof licensed amateur flag for a node CVSS 3.1HIGH 8.2
- TI-2024-34421 Failure to check for packets from the broadcast address allows potential DDoS… CVSS 3.1HIGH 7.5
- TI-2025-33563 Meshtastic allows Command Injection in GitHub Action CVSS 3.1HIGH 8.0
- TI-2025-18515 Meshtastic crashes via an unimplemented routing module reply CVSS 3.1MEDIUM 6.5
- TI-2025-33554 Meshtastic firmware allows forged DMs with no PKC to show up as encrypted CVSS 3.1MEDIUM 5.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences