CVE-2026-44359

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.8%, top 23% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 10.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
61(Track)
EG Risk 61/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation2% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
77%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 24, 2026

Advisory Details (4)

Auto-updated Sep 18, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Arbitrary Code Execution via pull_request_target Fork Checkout in CI Workflow · Advisory · meshtastic/firmware · GitHub

https://github.com/meshtastic/firmware/security/advisories/GHSA-mjx5-98jq-q736
github Patch Available

Command Injection in GitHub Action · Advisory · meshtastic/firmware · GitHub

https://github.com/meshtastic/firmware/security/advisories/GHSA-6mwm-v2vv-pp96
github_commit

commit 5716aeba3bc1 (meshtastic/firmware)

Fix landed in meshtastic/firmware commit 5716aeba3bc1 — awaiting tagged release

https://github.com/meshtastic/firmware/commit/5716aeba3bc1e1d34fba9567ff88917ede4a78a5
generic

github_actions_meshtastic_poc.mov - Google Drive

https://drive.google.com/file/d/1GdHT2s5hMYCiHt4zrWt1q58mvL7WQC0M/view?usp=sharing

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 106 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 04:06 UTCEG score recompute
  3. 2026-09-17 19:31 UTCEPSS rescore
  4. 2026-09-17 05:16 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 12:50 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-12 19:31 UTCEG score recompute
  9. 2026-09-12 15:01 UTCEPSS rescore
  10. 2026-09-11 18:37 UTCEG score recompute
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 09:38 UTCEG score recompute
  13. 2026-09-11 09:37 UTCEPSS rescore
  14. 2026-09-10 09:34 UTCEPSS rescore
  15. 2026-09-09 12:22 UTCEG score recompute
  16. 2026-09-08 22:00 UTCEPSS rescore
  17. 2026-09-07 23:03 UTCEG score recompute
  18. 2026-09-07 16:01 UTCEPSS rescore
  19. 2026-09-06 16:58 UTCEG score recompute
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-05 19:53 UTCEG score recompute
  22. 2026-09-05 09:44 UTCEG score recompute
  23. 2026-09-04 05:06 UTCEPSS rescore
  24. 2026-09-02 14:12 UTCEPSS rescore
  25. 2026-09-01 13:54 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 19:47 UTCEG score recompute
  2. 2026-08-30 19:17 UTCEPSS rescore
  3. 2026-08-30 02:43 UTCEG score recompute
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 21:21 UTCEG score recompute
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 22:13 UTCEG score recompute
  9. 2026-08-26 14:46 UTCEPSS rescore
  10. 2026-08-25 16:01 UTCEG score recompute
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-24 19:01 UTCEG score recompute
  13. 2026-08-24 12:15 UTCEG score recompute
  14. 2026-08-23 02:22 UTCEG score recompute
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-22 01:17 UTCEG score recompute
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-21 00:07 UTCEG score recompute
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-19 22:55 UTCEG score recompute
  21. 2026-08-19 17:04 UTCEPSS rescore
  22. 2026-08-18 19:38 UTCEG score recompute
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-16 19:12 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
  26. 2026-08-16 06:19 UTCEG score recompute
  27. 2026-08-16 02:14 UTCEPSS rescore
  28. 2026-08-15 05:14 UTCEG score recompute
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 00:00 UTCEG score recompute
  31. 2026-08-13 22:00 UTCEPSS rescore
  32. 2026-08-12 14:04 UTCEG score recompute
  33. 2026-08-12 13:51 UTCEPSS rescore
  34. 2026-08-11 17:08 UTCEG score recompute
  35. 2026-08-11 13:43 UTCEPSS rescore
  36. 2026-08-11 00:25 UTCEG score recompute
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-09 14:59 UTCEG score recompute
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-08 18:05 UTCEG score recompute
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-07 17:01 UTCEG score recompute
  43. 2026-08-06 15:57 UTCEG score recompute
  44. 2026-08-06 13:46 UTCEPSS rescore
  45. 2026-08-05 23:15 UTCEG score recompute
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-04 17:04 UTCEG score recompute
  48. 2026-08-04 15:10 UTCEPSS rescore
  49. 2026-08-04 12:53 UTCEG score recompute
  50. 2026-08-04 10:38 UTCEPSS rescore
  51. 2026-08-03 14:13 UTCEG score recompute
  52. 2026-08-03 10:36 UTCEPSS rescore
  53. 2026-08-02 04:08 UTCEG score recompute
  54. 2026-08-02 02:27 UTCEPSS rescore
  55. 2026-08-01 07:12 UTCEG score recompute
  56. 2026-08-01 04:16 UTCEPSS rescore
  57. 2026-07-30 17:11 UTCEG score recompute
  58. 2026-07-30 16:28 UTCEPSS rescore
  59. 2026-07-30 13:00 UTCEG score recompute
  60. 2026-07-30 04:35 UTCEG score recompute
  61. 2026-07-30 01:30 UTCEPSS rescore
  62. 2026-07-28 17:28 UTCEG score recompute
  63. 2026-07-28 15:36 UTCEPSS rescore
  64. 2026-07-27 16:11 UTCEG score recompute
  65. 2026-07-27 14:13 UTCEPSS rescore
  66. 2026-07-26 15:01 UTCEG score recompute
  67. 2026-07-26 14:54 UTCEPSS rescore
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-26 10:51 UTCEG score recompute
  70. 2026-07-26 04:31 UTCEG score recompute
  71. 2026-07-25 14:18 UTCEPSS rescore
  72. 2026-07-24 14:17 UTCEPSS rescore
  73. 2026-07-23 14:18 UTCEPSS rescore
  74. 2026-07-23 03:15 UTCEG score recompute
  75. 2026-07-22 23:54 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44359?
CVE-2026-44359 is a critical vulnerability published on July 19, 2026. Meshtastic is an open source mesh networking solution. Prior to version 2.7.21.1370b23, the Meshtastic GitHub repository's mainmatrix.yml workflow is triggered by pullrequesttarget and multiple jobs check out the attacker's fork code and execute it with access to repository secrets and elevated…
When was CVE-2026-44359 disclosed?
CVE-2026-44359 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44359 actively exploited?
CVE-2026-44359 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 22.5% of all scored CVEs.
What is the CVSS score of CVE-2026-44359?
CVE-2026-44359 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-44359?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44359, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-44359

Explore →

Is Your Infrastructure Affected by CVE-2026-44359?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs