Production compromise via privileged workflow_run deployment
Published Jun 11, 2026 · Updated Jun 11, 2026
Supply chain compromise in Vantern Quest Bot before 1.0.3 allows remote attackers to deploy arbitrary production bot code via a pull request. The workflow_run deploy workflow trusts a successful build and a main head_branch value, then checks out the triggering head_sha, builds its Dockerfile, pushes it as latest, and invokes the deployment webhook. Exploitation requires pull-request Actions, a privileged deploy workflow, deployment permissions, and a configured webhook; success exposes the production bot environment and permits malicious image publication.
Summary
What happened
Supply chain compromise in Vantern Quest Bot before 1.0.3 allows remote attackers to deploy arbitrary production bot code via a pull request. The workflow_run deploy workflow trusts a successful build and a main head_branch value, then checks out the triggering head_sha, builds its Dockerfile, pushes it as latest, and invokes the deployment webhook. Exploitation requires pull-request Actions, a privileged deploy workflow, deployment permissions, and a configured webhook; success exposes the production bot environment and permits malicious image publication.
The record
- CVE
- CVE-2026-47172
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- Vantern
- Product
- Quest Bot
- Classifications
- CWE-829, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 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.0.3
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
- GitHub advisory pull-request deployment 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