// Security Advisory Triage

Apigee outbound TLS vulnerable to MITM via compromised eMudhra intermediate keys

Google Cloud security bulletins · published 2026-11-11 05:23 UTC
ACTION NEEDED MITIGATE SECURITY
WHAT CHANGEDGoogle published GCP-2026-077 on 2026-11-03, disclosing that eMudhra's emSign ECC Root CA - G3 intermediate keys were compromised. Outbound TLS connections from Apigee runtimes (TargetEndpoints, TargetServers, ServiceCallouts, and outbound JWKS policy lookups) using default or unmanaged system trust stores may accept fraudulent certificates issued by an attacker with the compromised keys. CVE-2026-111943 and CVE-2026-91403 are assigned.
WHY IT MATTERSAn attacker with the compromised intermediate keys can issue valid-looking TLS certificates for any domain. Apigee proxies making outbound HTTPS calls to backend services will accept these forged certificates, allowing the attacker to intercept, read, or modify traffic between Apigee and your backends.
WHAT TO DOFollow the remediation steps in the Apigee security bulletin linked from GCP-2026-077. This applies to Apigee, Apigee Hybrid, Apigee Edge (SaaS), and Apigee Edge for Private Cloud (OPDK). Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-077 Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-077.
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## GCP-2026-077
+https://docs.cloud.google.com/support/bulletins/index#gcp-2026-077
+2026-11-03T21:33:38.108087+00:00
+
+Published: 2026-11-03Description
+
+Description
+Severity
+Notes
+
+Following the private-key compromise of intermediate Certificate
+Authorities (CAs) associated with eMudhra (emSign), outbound TLS
+connections trusting affected roots—specifically
+emSign ECC Root CA - G3—are vulnerable to
+Man-in-the-Middle (MITM) interception. An attacker possessing
+compromised intermediate keys can issue fraudulent TLS certificates for
+arbitrary domain names. Outbound HTTPS connections made from
+Apigee runtimes (such as TargetEndpoints, TargetServers,
+ServiceCallouts, and outbound JWKS policy lookups) using default or
+unmanaged system trust stores may accept forged certificates. This
+security bulletin outlines required remediation steps for
+Apigee, Apigee Hybrid, Apigee Edge (SaaS),
+and Apigee Edge for Private Cloud (OPDK).
+For more information, see the
+Apigee security bulletin.
+
+Medium
+
+CVE-2026-111943
+CVE-2026-91403
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningCompromised CA keys enable MITM attacks on Apigee outbound connections; affects managed runtime trust stores.
signalscloud control plane / managed service (Apigee) · known CA compromise (eMudhra intermediate keys) · MITM vulnerability in outbound TLS from managed runtime · affects default trust stores in customer-facing service · multiple CVEs assigned · remediation required per bulletin
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)