Security readout for executives and security teams
Plain-English summary
A flaw in Meshtastic’s GitHub build automation allowed an external pull request to run untrusted fork code with repository secrets and elevated permissions. This could have enabled repository, build-system, or software supply-chain compromise. The supplied evidence identifies the project’s CI repository—not deployed mesh devices—as the direct attack surface.
Executive priority
Immediate for Meshtastic maintainers and organizations operating a copy of the affected CI workflow. Patch first, then investigate historical external pull-request runs and rotate potentially exposed credentials. Firmware consumers should monitor vendor guidance and verify artifact provenance; the supplied evidence does not show their deployed devices were directly attacked.
Technical view
Before 2.7.21.1370b23, main_matrix.yml used pull_request_target while several jobs checked out and executed fork-controlled code. External contributors with author_association "NONE" required no approval. Execution occurred with repository secrets and elevated GITHUB_TOKEN permissions, creating potential code execution, self-hosted runner compromise, unauthorized repository changes, and compromised build outputs.
Likely exposure
Direct exposure applies to the Meshtastic firmware repository and any equivalent retained workflow configuration before 2.7.21.1370b23. Risk is greatest where external pull requests ran automatically, secrets were available, or self-hosted runners were used. The bundle does not establish direct remote exploitation of installed Meshtastic devices.
Exploitation context
The CVSS 3.1 score is 10.0 because an unauthenticated external contributor could potentially trigger execution without user interaction. However, the CVE is not listed as KEV, and the supplied sources do not confirm active exploitation or a completed compromise. Treat historical qualifying workflow runs as potentially exposed pending investigation.
Researcher notes
This issue is distinct from GHSA-6mwm-v2vv-pp96, which addressed command injection involving github.head_ref in the setup job. According to the bundle, that change did not resolve fork checkout and execution across the check, build, and build-debian-src jobs. Evidence supports severe potential impact, but not confirmed exploitation.
Mitigation direction
- Update the repository workflow to version 2.7.21.1370b23 or later.
- Disable affected CI jobs until the patched workflow is deployed.
- Rotate repository secrets if untrusted fork code may have executed.
- Review and restrict GITHUB_TOKEN permissions to the minimum required.
- Rebuild sensitive artifacts from a trusted, verified environment after suspected exposure.
Validation and detection
- Confirm the repository contains version 2.7.21.1370b23 or later.
- Verify pull_request_target jobs never execute code checked out from untrusted forks.
- Review historical runs triggered by external users with author_association "NONE".
- Audit repository changes, releases, artifacts, secrets access, and runner activity around those runs.
- Confirm self-hosted runners used by affected jobs were investigated or rebuilt.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-829: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-44359 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N3.95.8GitHub_MVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/meshtastic/firmware/security/advisories/GHSA-mjx5-98jq-q736CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/meshtastic/firmware/security/advisories/GHSA-6mwm-v2vv-pp96CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/meshtastic/firmware/commit/5716aeba3bc1e1d34fba9567ff88917ede4a78a5CVE reference, GitHub_M · x_refsource_MISC
- https://drive.google.com/file/d/1GdHT2s5hMYCiHt4zrWt1q58mvL7WQC0M/view?usp=sharingCVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.