CVE-2026-44359 is a critical CI/CD supply-chain vulnerability in the Meshtastic GitHub repository affecting versions prior to 2.7.21.1370b23. The flaw resides in the main_matrix.yml GitHub Actions workflow, which is triggered by pull_request_target and then, in multiple jobs including check, build, and build-debian-src, checks out and executes code from an external contributor's fork. Because pull_request_target runs in the security context of the target repository, the attacker-controlled code executes with access to repository secrets and elevated GITHUB_TOKEN permissions. The workflow lacked an approval gate for untrusted external pull requests, including those from users with no prior repository trust relationship. This created a condition where arbitrary code from an attacker-controlled fork could run directly in CI with privileged repository context, enabling compromise of the build pipeline and repository environment.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.