CVE-2026-59335: CWE-178: Improper Handling of Case Sensitivity in Cloud Foundry UAA

The vulnerability stems from a mismatch in case sensitivity handling between the authorization layer and the MySQL persistence layer in Cloud Foundry UAA. The authorization layer compares zone identifiers case-sensitively, while MySQL's default collation is case-insensitive. An attacker with zones.write authority can exploit this by specifying the system zone identifier in a non-lowercase form (e.g., 'UAA'), causing the authorization check to incorrectly permit access. This allows overwriting the system zone's JWT signing key with attacker-controlled keys, enabling JWT forgery with admin privileges and full compromise of UAA and any trusting Cloud Foundry deployment. This issue only affects UAA deployments using MySQL with default collation; other database backends like PostgreSQL and HSQLDB are not vulnerable.

An attacker with zones.write authority can bypass intended access restrictions to the privileged system identity zone, overwrite critical JWT signing keys, forge administrator-level JWT tokens, and fully compromise the UAA service and any Cloud Foundry deployments relying on it. This leads to complete loss of integrity and trust in authentication and authorization mechanisms within affected environments.

No patch or official fix information is provided in the available data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict zones.write authority to fully trusted users and consider deploying UAA with PostgreSQL or HSQLDB backends, which are not affected by this vulnerability.