Repository code injection via unsafe branch interpolation
Published Jul 10, 2025 · Updated Jul 11, 2025
Command injection in Meshtastic Firmware 2.5.3 through 2.6.5 allows remote authenticated users to expose runner secrets via a crafted pull request. The main_matrix.yml workflow interpolates github.ref_name directly into a shell echo command executed by a privileged pull_request_target job. A fork contributor must open a pull request with a command-substitution branch name; execution can disclose the GitHub token and permit unauthorized repository changes.
Summary
What happened
Command injection in Meshtastic Firmware 2.5.3 through 2.6.5 allows remote authenticated users to expose runner secrets via a crafted pull request. The main_matrix.yml workflow interpolates github.ref_name directly into a shell echo command executed by a privileged pull_request_target job. A fork contributor must open a pull request with a command-substitution branch name; execution can disclose the GitHub token and permit unauthorized repository changes.
The record
- CVE
- CVE-2025-53637
- Published
- Jul 10, 2025
- Updated
- Jul 11, 2025
- Vendor
- Meshtastic
- Product
- Meshtastic Firmware
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 10, 2025CVE publishedPublication date reported by the CVE source.
- Jul 11, 2025Record 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.
- Affected versionversion=>= 2.5.3, < 2.6.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- Crafted branch-name command injection proof of conceptproof of concept · demonstrated
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