Runner command execution via untrusted pull request names
Published Aug 28, 2026 · Updated Aug 28, 2026
OS command injection in JS Recon allows remote attackers to execute commands on its GitHub Actions runner through a crafted pull request. The PR Branch Checker assigns pull request branch and fork names to BRANCH_NAME and SOURCE_REPO, then expands them unquoted inside a gh pr comment shell command. Exploitation requires a pull request targeting main; injected commands run with the workflow's pull-requests write token.
Summary
What happened
OS command injection in JS Recon allows remote attackers to execute commands on its GitHub Actions runner through a crafted pull request. The PR Branch Checker assigns pull request branch and fork names to BRANCH_NAME and SOURCE_REPO, then expands them unquoted inside a gh pr comment shell command. Exploitation requires a pull request targeting main; injected commands run with the workflow's pull-requests write token.
The record
- CVE
- CVE-2026-55378
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- Shriyans Sudhi
- Product
- JS Recon
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 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.
- Affected versionversion=>= 1.2.1-beta.1, < 1.3.1-beta.2
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
No public exploit references are available in this record.
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