OAuth2 token disclosure via cross-request state reuse
Published Aug 21, 2026 · Updated Aug 21, 2026
Sensitive-data exposure in Apache CloudStack allows attackers to obtain OAuth2 tokens belonging to other authentication requests. The OAuth2 plugin's Google integration reuses token-bearing state across requests instead of isolating it to the originating login flow. OAuth2 is disabled by default; exposure requires an enabled, configured Google provider and overlapping or successive authentication requests.
Summary
What happened
Sensitive-data exposure in Apache CloudStack allows attackers to obtain OAuth2 tokens belonging to other authentication requests. The OAuth2 plugin's Google integration reuses token-bearing state across requests instead of isolating it to the originating login flow. OAuth2 is disabled by default; exposure requires an enabled, configured Google provider and overlapping or successive authentication requests.
The record
- CVE
- CVE-2026-61397
- Published
- Aug 21, 2026
- Updated
- Aug 21, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache CloudStack
- Classifications
- CWE-200, T1528
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 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=4.19.0.0 <=4.20.3.0
- Affected versionversion=4.21.0.0 <=4.22.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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