Code execution via Mercurial revision option injection
Published Jul 2, 2026 · Updated Jul 2, 2026
OS command injection in Open Build Service before 0.12.4 allows attackers to execute code through a crafted _service file. The TarSCM Mercurial switch_revision path appended the attacker-controlled revision to hg update without an end-of-options delimiter, so Mercurial parsed it as command-line options. The attacker must supply a service definition selecting Mercurial; code runs as the source-service account or a local user processing the malicious checkout.
Summary
What happened
OS command injection in Open Build Service before 0.12.4 allows attackers to execute code through a crafted _service file. The TarSCM Mercurial switch_revision path appended the attacker-controlled revision to hg update without an end-of-options delimiter, so Mercurial parsed it as command-line options. The attacker must supply a service definition selecting Mercurial; code runs as the source-service account or a local user processing the malicious checkout.
The record
- CVE
- CVE-2026-56004
- Published
- Jul 2, 2026
- Updated
- Jul 2, 2026
- Vendor
- OpenSUSE
- Product
- Open Build Service
- Classifications
- CWE-78, CAPEC-242, T1059.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 2, 2026CVE publishedPublication date reported by the CVE source.
- Jul 2, 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=0 <0.12.4
What conditions does exploitation require?
What is affected?
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