CVE-2026-44359
GitHub Actions workflow let attacker forks run code with repo secrets (RCE).
Is CVE-2026-44359 being exploited?
Not confirmed. CVE-2026-44359 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.8% probability of exploitation in the next 30 days.
How severe is CVE-2026-44359?
CVE-2026-44359 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44359?
Yes. A fix has been recorded for CVE-2026-44359. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44359 affect?
CVE-2026-44359 affects Meshtastic <2.7.21.1370b23, GitHub Actions main_matrix.yml workflow, Self-hosted runners, Repository secrets / GITHUB_TOKEN. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44359?
Update to >=2.7.21.1370b23; rotate secrets; audit runners and workflows.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-controlled fork code executed via pull_request_target, enabling remote code execution, access to repo secrets/GITHUB_TOKEN, self-hosted runner compromise, and repo takeover.
Immediate action required
- affected< 2.7.21.1370b23
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.