Repository compromise via workflow expression injection
Published Sep 30, 2025 · Updated Sep 30, 2025
Command injection in serverless-dns before 0.1.31 allows remote attackers to write arbitrary data to its repository via a pull request. The pr.yml pull_request_target workflow expands attacker-controlled clone_url and head_ref expressions directly inside shell commands instead of passing them through environment variables. No repository account is required; the workflow token's write permission lets injected commands alter repository content that end users later execute.
Summary
What happened
Command injection in serverless-dns before 0.1.31 allows remote attackers to write arbitrary data to its repository via a pull request. The pr.yml pull_request_target workflow expands attacker-controlled clone_url and head_ref expressions directly inside shell commands instead of passing them through environment variables. No repository account is required; the workflow token's write permission lets injected commands alter repository content that end users later execute.
The record
- CVE
- CVE-2025-61584
- Published
- Sep 30, 2025
- Updated
- Sep 30, 2025
- Vendor
- serverless-dns
- Product
- serverless-dns
- Classifications
- CWE-77, T1677
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 30, 2025CVE publishedPublication date reported by the CVE source.
- Sep 30, 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=< 0.1.31
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