CVE-2026-44359Public exploitNetwork attack vector

Repository takeover via untrusted pull request checkout

Published Jul 19, 2026 · Updated Jul 19, 2026

Code execution in Meshtastic Firmware before 2.7.21.1370b23 allows remote attackers to compromise its GitHub build pipeline. The main_matrix.yml pull_request_target workflow checks out files from an external contributor's fork and runs attacker-controlled build and check scripts with inherited secrets and elevated GITHUB_TOKEN permissions. An unauthenticated external contributor needs only to open a pull request; automatic execution can expose signing keys, persist on self-hosted runners, or grant write access to repository content and releases.

CVSS severity10.0
Critical
EPSS probability1.80%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Code execution in Meshtastic Firmware before 2.7.21.1370b23 allows remote attackers to compromise its GitHub build pipeline. The main_matrix.yml pull_request_target workflow checks out files from an external contributor's fork and runs attacker-controlled build and check scripts with inherited secrets and elevated GITHUB_TOKEN permissions. An unauthenticated external contributor needs only to open a pull request; automatic execution can expose signing keys, persist on self-hosted runners, or grant write access to repository content and releases.

The record

CVE
CVE-2026-44359
Published
Jul 19, 2026
Updated
Jul 19, 2026
Vendor
Meshtastic
Product
Meshtastic Firmware
Classifications
CWE-829, CWE-94, T1195.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.7.21.1370b23

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Meshtastic · Meshtastic Firmwareversion=< 2.7.21.1370b23

Published CVSS scores

10.0GitHubCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-829Inclusion of Functionality from Untrusted Control Sphere
CWE-94Improper Control of Generation of Code ('Code Injection')
T1195.001Compromise Software Dependencies and Development Tools

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo