Unauthenticated token impersonation via unsigned SAML assertions
Published Apr 16, 2026 · Updated Apr 16, 2026
Authentication bypass in Cloud Foundry UAA 77.21.0 through 78.8.0 allows remote attackers to obtain tokens for arbitrary users. The SAML 2.0 bearer grant accepts assertions carrying neither a signature nor encryption and treats supplied identities as authenticated. Exposure requires SAML 2.0 bearer assertions to be enabled for a client; issued tokens grant access to UAA-protected systems as the impersonated user.
Summary
What happened
Authentication bypass in Cloud Foundry UAA 77.21.0 through 78.8.0 allows remote attackers to obtain tokens for arbitrary users. The SAML 2.0 bearer grant accepts assertions carrying neither a signature nor encryption and treats supplied identities as authenticated. Exposure requires SAML 2.0 bearer assertions to be enabled for a client; issued tokens grant access to UAA-protected systems as the impersonated user.
The record
- CVE
- CVE-2026-22734
- Published
- Apr 16, 2026
- Updated
- Apr 16, 2026
- Vendor
- Cloud Foundry Foundation
- Product
- User Account and Authentication (UAA)
- Classifications
- CWE-290, CAPEC-646, T1606.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2026CVE publishedPublication date reported by the CVE source.
- Apr 16, 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=v77.21.0 <=v78.8.0
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