CVE-2026-59335
HighCVSS 8.7Exploitation Probability (EPSS)
Low risk22th percentile - higher than 22% of all known CVEs
Summary
Improper handling of case sensitivity (CWE-178) in the identity zone authorization check in the Identity Zone Endpoint in Cloud Foundry UAA allows a remote authenticated attacker holding only the zones.write authority to bypass the intended restriction that this authority does not grant access to the privileged uaa (system) identity zone, by referring to the zone identifier in a non-lowercase form (e.g. UAA) in the request path and body. The authorization layer performs a case-sensitive comparison against the system zone identifier, while the underlying MySQL persistence layer resolves identifiers case-insensitively under its default collation, so the request is authorized incorrectly and is then resolved against the real system zone record. This allows the attacker to overwrite the system zone's JWT signing key with attacker-controlled key material, forge JWTs claiming the admin client and administrator scopes, and fully compromise UAA and any Cloud Foundry deployment that trusts it. This issue only affects UAA deployments backed by MySQL using its default collation; PostgreSQL and HSQLDB backends are not affected.
Risk Assessment
An attacker can gain full control over UAA and the entire Cloud Foundry deployment, potentially leading to unauthorized access to applications and data.
Recommendation
Change the default MySQL collation to case-sensitive or update UAA to a version with a fix.
Other vulnerabilities in Cloud Foundry UAA
See all- CVE-2017-4963High
An issue was discovered in Cloud Foundry affecting versions v252 and earlier, as well as UAA versions from v2.0.0 to v2.7.4.12 and from v3.0.0 to v3.11.0. UAA is vulnerable to session fixation when configured to authenticate against external SAML or OpenID Connect based identity providers.
- CVE-2017-4960High
An issue was discovered in Cloud Foundry release v247 through v252 and UAA release v3.9.0 through v3.11.0 that may lead to a denial of service attack on UAA OAuth clients.
- CVE-2016-6659High
Cloud Foundry and UAA versions before 248; UAA 2.x before 2.7.4.12, 3.x before 3.6.5, and 3.7.x through 3.9.x before 3.9.3 have a vulnerability that allows attackers to gain privileges by accessing UAA logs and subsequently running a specially crafted application that interacts with a configured SAML provider.
- CVE-2026-40965Critical
Cloud Foundry UAA versions v76.12.0 through v78.12.0 inadvertently expose EC private keys through the public /token_keys endpoint. The vulnerability affects only deployments using EC keys for JWT token signing.
Original NVD description (English source)
Improper handling of case sensitivity (CWE-178) in the identity zone authorization check in the Identity Zone Endpoint in Cloud Foundry UAA allows a remote authenticated attacker holding only the zones.write authority to bypass the intended restriction that this authority does not grant access to the privileged uaa (system) identity zone, by referring to the zone identifier in a non-lowercase form (e.g. UAA) in the request path and body. The authorization layer performs a case-sensitive comparison against the system zone identifier, while the underlying MySQL persistence layer resolves identifiers case-insensitively under its default collation, so the request is authorized incorrectly and is then resolved against the real system zone record. This allows the attacker to overwrite the system zone's JWT signing key with attacker-controlled key material, forge JWTs claiming the admin client and administrator scopes, and fully compromise UAA and any Cloud Foundry deployment that trusts it. This issue only affects UAA deployments backed by MySQL using its default collation; PostgreSQL and HSQLDB backends are not affected.