# CVE-2026-19410: Google Cloud Build Comment Control Bypass via Webhook Suppression

> Remote attackers can execute unreviewed code in Google Cloud Build environments by bypassing comment controls via webhook suppression.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/U:Clear`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-q4ww-hvh7-426w

## What is CVE-2026-19410?

CVE-2026-19410 is a critical missing authorization vulnerability in Google Cloud Build, published on 31 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-19410?


## How do I fix CVE-2026-19410?

No fix has been published for CVE-2026-19410 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19410 being exploited?

There is no known exploitation of CVE-2026-19410 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19410 and fix it if it is affected.

What it is: CVE-2026-19410 is a critical missing authorization vulnerability in Google Cloud Build, published on 31 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-19410 in the wild and no public exploit code.

Affected product: Google Cloud Build. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19410/ (Markdown: https://insights.sbomify.com/CVE-2026-19410/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19410
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19410
- OSV: https://osv.dev/vulnerability/CVE-2026-19410

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19410/
Summaries are generated and may contain mistakes; the official description above is the record.