Unauthenticated code execution via comment-control bypass
Published Mar 3, 2026 · Updated Mar 3, 2026
Improper authorization in Google Cloud Build before 1/26/2026 allows remote attackers to execute arbitrary code in the build environment. The affected GitHub Trigger Comment Control path is intended to require approval from a repository writer, but Google has not published the faulty internal operation. Exploitation requires a GitHub pull-request interaction and grants code execution within the victim build environment.
Summary
What happened
Improper authorization in Google Cloud Build before 1/26/2026 allows remote attackers to execute arbitrary code in the build environment. The affected GitHub Trigger Comment Control path is intended to require approval from a repository writer, but Google has not published the faulty internal operation. Exploitation requires a GitHub pull-request interaction and grants code execution within the victim build environment.
The record
- CVE
- CVE-2026-3136
- Published
- Mar 3, 2026
- Updated
- Mar 3, 2026
- Vendor
- Go standard library
- Product
- Cloud Build
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 2026CVE publishedPublication date reported by the CVE source.
- Mar 3, 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 <1/26/2026
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.
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