CVE-2026-44359
CRITICALDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Exploit Intelligence
Moderate risk: more likely to be exploited than 60% of all known CVEs.
References
Related Vulnerabilities
Other CWE-94 (Code Injection) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-9841 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2015-1635 | Critical | 9.8 | 100% | KEV | - |
| CVE-2025-3248 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2022-22954 | Critical | 9.8 | 100% | KEV + Ransom | - |
| CVE-2021-22204 | Medium | 6.8 | 100% | KEV | Fix |
| CVE-2012-0158 | High | 8.8 | 100% | KEV | - |
Common questions
How do I fix CVE-2026-44359?
No published fix for CVE-2026-44359 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-44359 being actively exploited?
Not that we know of. CVE-2026-44359 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 1.0% is the estimated probability that it will be exploited in the next 30 days. That is higher than 60% of all scored CVEs.
How severe is CVE-2026-44359?
CVE-2026-44359 has a CVSS v3 base score of 10.0, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-44359
Markdown
[](https://tridentstack.com/cve/CVE-2026-44359)HTML
<a href="https://tridentstack.com/cve/CVE-2026-44359"><img src="https://tridentstack.com/cve/badge/CVE-2026-44359.svg" alt="CVE-2026-44359"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-24.