CVE-2026-2264
A critical vulnerability in Google Cloud Apigee’s SetIntegrationRequest policy allows attackers to perform server‑side request forgery and steal service‑account tokens. The flaw requires an insecure API‑proxy configuration. If exploited, attackers can read sensitive data from internal services.
No official fix yet. If none appears within 45 days of first tracking, this entry is removed automatically.
Who is affected
Google Cloud Apigee API proxies that use the SetIntegrationRequest policy and are configured insecurely.
Real-world impact
An attacker could send crafted requests that force the Apigee proxy to reach internal endpoints, retrieving service‑account access tokens and potentially accessing other internal resources.
Why this severity
The CVSS score of 9.2 reflects the combination of high confidentiality, integrity, and availability impact, low attack complexity, and the need for no privileges or user interaction.
What to do about it
- ›Review the SetIntegrationRequest policy configuration and remove any insecure settings that allow SSRF.
- ›Ensure that the API proxy does not expose internal endpoints or allow arbitrary URLs in the policy.
No official fix or mitigation is documented in the sources yet. Monitor the vendor advisory and apply the patch as soon as it is released.
NVD description
Timeline
- May 26, 2026 · May 26, 2026PublishedDisclosed and added to the National Vulnerability Database.
- Jul 24, 2026 · 11d agoAdvisory updatedThe NVD record was last revised.