Security Advisory Desk
unratedQCS priority 76/100Google Cloud

GCP-2026-087

Two serious security flaws were found in the HTTP/2 module of nginx, a widely used web server software. These flaws could allow attackers who do not have any login credentials to remotely run harmful code on servers using vulnerable nginx versions when they accept HTTP/2 connections. Google Cloud's Apigee Edge for Private Cloud routers run affected versions of nginx, but are not at risk under their default configurations because HTTP/2 is disabled by default on router virtual hosts. The vulnerabilities have been fixed in the newer nginx version 1.30.7.

QCS published 20/11/2026, 3:59:32 pm ISTVendor disclosure 20/11/2026, 7:53:07 am ISTVerified 20/11/2026, 3:59:32 pm ISTRevision 1

In plain language

What this advisory means

Two serious security flaws were found in the HTTP/2 module of nginx, a widely used web server software. These flaws could allow attackers who do not have any login credentials to remotely run harmful code on servers using vulnerable nginx versions when they accept HTTP/2 connections. Google Cloud's Apigee Edge for Private Cloud routers run affected versions of nginx, but are not at risk under their default configurations because HTTP/2 is disabled by default on router virtual hosts. The vulnerabilities have been fixed in the newer nginx version 1.30.7.

Technical explanation

How the issue affects the environment

The vulnerabilities, identified as CVE-2026-123633 and CVE-2026-123007, exist in the nginx HTTP/2 module. They allow remote, unauthenticated attackers to execute arbitrary code on nginx servers that support HTTP/2 protocol connections. The Apigee Edge for Private Cloud routers version 4.54.00 and 4.53.01 use nginx versions in the vulnerable range. However, these routers are not affected in their default and supported configurations as HTTP/2 support on router virtual hosts is disabled. Both vulnerabilities are corrected in nginx version 1.30.7.

Operational impact

Why teams should care

If exploited, these vulnerabilities could enable attackers to fully compromise vulnerable nginx servers by remotely executing arbitrary code without authentication, potentially leading to data breaches, service disruption, or further network compromise. While Apigee Edge routers use affected nginx versions, the default settings prevent HTTP/2 traffic, thus mitigating risk unless configurations are changed. Customers must evaluate their usage of HTTP/2 in nginx instances and Apigee router configurations to assess exposure.

Immediate action

Upgrade any nginx servers that accept HTTP/2 connections to nginx version 1.30.7 or later to eliminate these vulnerabilities. For Apigee Edge for Private Cloud users, verify that the Router virtual hosts remain configured without HTTP/2 enabled; if HTTP/2 must be enabled, upgrade nginx to version 1.30.7 or later. Review the official Apigee security bulletin for detailed guidance and follow recommended security updates.

Affected and fixed releases

Affected versionsApigee Edge for Private Cloud 4.54.00, Apigee Edge for Private Cloud 4.53.01 (nginx version in affected range)
Fixed versionsnginx 1.30.7

Temporary risk reduction

For Apigee Edge for Private Cloud Routers, maintaining the default configuration which does not support HTTP/2 on Router virtual hosts serves as a practical workaround, mitigating exposure to these vulnerabilities. Disabling HTTP/2 support on nginx servers also reduces risk temporarily but upgrading remains the definitive remediation.

Evidence and validation checklist

  • Official Google Cloud Security Bulletin GCP-2026-087 confirms the nginx HTTP/2 vulnerabilities and the affected Apigee Edge versions.
  • The bulletin states that routers are not affected in default configurations because HTTP/2 is disabled on router virtual hosts.
  • The vulnerabilities are fixed in nginx 1.30.7 as per the original advisory.
  • The advisory includes CVE identifiers CVE-2026-123633 and CVE-2026-123007.
  • No known exploitation reports or workarounds besides configuration mentioned in the bulletin.

Authoritative reference

Google Cloud Security Bulletins

QCS detected and normalized this record from the official source. Vendor guidance remains authoritative.

Open source