Secuno
ENNL
Book demo

CVE-2026-3136

Google Cloud Build remote code execution

9.8 CRITICALEPSS 0.41%
  1. Published3 Mar 2026

Description

An improper authorization vulnerability in GitHub Trigger Comment Control in Google Cloud Build prior to 2026-1-26 allows a remote attacker to execute arbitrary code in the build environment. This vulnerability was patched on 26 January 2026, and no customer action is needed.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Google Cloud Build< 2026-1-26

Remediation

Fixed in
Google Cloud Build≥ 2026-1-26

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1095598.7
EdgeEver Desktop 1.6.26 through 1.112.0 contains a navigation allowlist bypass that…
CVE-2026-773669.9
obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian…
CVE-2026-1039038.8
An incorrect authorization vulnerability in the WinBox authentication flow of MikroTik…
CVE-2026-1087468.8
Vearch 3.5.2 through 3.5.9 contains an incorrect authorization vulnerability in…
CVE-2026-816499.1
The Fundiin cho WooCommerce WordPress plugin through 3.4.0 does not have proper…
CVE-2026-1085508.8
SkillHub before 0.2.22 contains an incorrect authorization vulnerability in…

Frequently asked

Is CVE-2026-3136 being actively exploited?

CVE-2026-3136 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.41%.

How severe is CVE-2026-3136?

CVE-2026-3136 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.41% probability of exploitation.

Which products are affected by CVE-2026-3136?

Affected products include Google Cloud Build.

How do I fix CVE-2026-3136?

Upgrade affected software to a fixed version, for example Google Cloud Build 2026-1-26 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-3136 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.