Service account token exfiltration via unvalidated IntegrationRegion
Published May 26, 2026 · Updated May 26, 2026
SSRF in Google Apigee's SetIntegrationRequest policy allows remote attackers to exfiltrate service account access tokens. The policy fails to validate an IntegrationRegion flow variable and sends a request bearing the service account token to the attacker-controlled host it names. Exploitation requires an administrator to configure an API proxy so an attacker can control the flow variable used for IntegrationRegion.
Summary
What happened
SSRF in Google Apigee's SetIntegrationRequest policy allows remote attackers to exfiltrate service account access tokens. The policy fails to validate an IntegrationRegion flow variable and sends a request bearing the service account token to the attacker-controlled host it names. Exploitation requires an administrator to configure an API proxy so an attacker can control the flow variable used for IntegrationRegion.
The record
- CVE
- CVE-2026-2264
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- Go standard library
- Product
- Apigee
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.14.4
- Affected versionversion=0 <1.15.2
- Affected versionversion=0 <1.16.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo