Google Cloud Build GitHub Trigger Comment Control authorization bypass enables unreviewed code execution

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-19410?

CVE-2026-19410 is a vulnerability classified as Time-of-check Time-of-use (TOCTOU) Race Condition and Insufficient Verification of Data Authenticity, affecting Google Cloud Build (affected versions: < 2026-06-24). This vulnerability is rated Critical, with a CVSS score of 9.4. Current sources do not report this vulnerability as exploited.

Overview

Original source data

An Incorrect Authorization vulnerability in GitHub Trigger Comment Control in Google Cloud Build prior to 2026-06-24 on Google Cloud Platform allows a remote attacker to execute unreviewed code in the build environment using webhook suppression. This vulnerability was patched on 24 June 2026, and no customer action is needed.

Affected products and scope

  • Google Cloud, Google Cloud Build: The CNA record marks the service as affected when the date-based version is less than 2026-06-24; the range is encoded with version 0 and the condition lessThan: 2026-06-24.
  • Fix boundary: Google Cloud states that the issue in GitHub Trigger Comment Control was fixed on June 24, 2026.
  • Status outside the listed range: The affected data sets default_status to unaffected, but it does not enumerate separate parallel release branches or customer-deployed product versions. The status of an unverified branch should not be inferred from this fix boundary alone.

Technical details

The affected component is GitHub Trigger Comment Control in Google Cloud Build. The authorization flaw lets a remote attacker use webhook suppression to cause unreviewed code to execute in the build environment. The record maps the issue to CWE-367, a time-of-check time-of-use race condition, and CWE-345, insufficient verification of data authenticity. The supplied attack characterization indicates network reachability, low required privileges, and low attack complexity; user interaction is classified as passive. The available evidence does not establish the exact check and use ordering, the required permission set, or the webhook message sequence needed to trigger the flaw.

Exploitability

  • Reachability: A remote attacker can reach the vulnerable functionality over the network.
  • Privileges and complexity: The supplied attack characterization specifies low required privileges and low attack complexity.
  • User interaction: The record classifies user interaction as passive.
  • Exploitation status: The supplied record does not identify widespread exploitation or a public exploit, and the returned vulnerability record includes an assessment of exploitation as none and automatable as no. These assessments do not prove that no exploitation attempts have occurred.

Technical impact

The confirmed technical outcome is execution of unreviewed code in the build environment through a comment-control bypass using webhook suppression. A successful abuse could affect build and artifact integrity and could also affect the confidentiality or availability of resources that the build is authorized to access. Those broader consequences depend on the build's actual permissions and resources and are not confirmed as having occurred. The flaw could create substantial software supply-chain risk if an artifact is created or released without the expected review gate. The record does not describe persistence, access to a specific data store, or impact beyond the build environment.

Business impact

The flaw can weaken the code review gate in CI/CD workflows, allowing a build to run code that was not reviewed as expected. If that code can access resources, data, or credentials available to the build, the organization could face risks to artifact integrity, build-accessible data, and pipeline continuity. The practical consequences depend on the permissions granted to the build service account, the resources exposed to the build, and the organization's artifact release process. The record does not name a campaign, victim, data breach, or specific incident.

Remediation

  1. No customer action is required according to Google Cloud: the service-side fix was applied on June 24, 2026.
  2. If validation is required for audit or change-management purposes, review Cloud Build usage of GitHub Trigger Comment Control and confirm that the service is covered by the post-fix state. The record does not provide a customer-facing version to upgrade.
  3. Inventory the relevant triggers and retain the build, webhook, and audit records needed for retrospective review.
  4. Do not apply an assumed package upgrade or configuration change. The available advisory does not provide an additional customer-side mitigation.

Detection

  1. Inventory Cloud Build projects and identify triggers that use GitHub Trigger Comment Control.
  2. Verify that those triggers are covered by the service state after the June 24, 2026 fix boundary, because the record provides no customer-visible product version to check.
  3. Review build and webhook history for unreviewed or unexpected build executions, especially activity associated with webhook suppression.
  4. Correlate anomalous builds with internal audit records and repository change history. This is precautionary monitoring, not a confirmed indicator list.
  5. Do not treat the absence of suspicious records as proof that an environment was not exposed.
Sources (17)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.