# CVE-2026-59335: Case-Sensitive Authorization Check Bypass via Identity Zone ID Case Manipulation Leads to Full UAA Compromise

> Authenticated attackers can bypass authorization checks to compromise the system identity zone and forge admin JWTs in MySQL-backed Cloud Foundry UAA deployments.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-m647-7qf2-2rmg

## What is CVE-2026-59335?

CVE-2026-59335 is a high-severity authentication bypass vulnerability in Cloud Foundry UAA, published on 25 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-178 (Improper Handling of Case Sensitivity)

## Which versions are affected by CVE-2026-59335?


## How do I fix CVE-2026-59335?

No fix has been published for CVE-2026-59335 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59335 being exploited?

There is no known exploitation of CVE-2026-59335 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59335 and fix it if it is affected.

What it is: CVE-2026-59335 is a high-severity authentication bypass vulnerability in Cloud Foundry UAA, published on 25 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59335 in the wild and no public exploit code.

Affected product: Cloud Foundry UAA. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59335/ (Markdown: https://insights.sbomify.com/CVE-2026-59335/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59335
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59335
- OSV: https://osv.dev/vulnerability/CVE-2026-59335

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59335/
Summaries are generated and may contain mistakes; the official description above is the record.