CVE-2026-59335
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 22% of all known CVEs.
References
Related Vulnerabilities
Other CWE-178 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-27636 | Medium | 5.6 | 81% | - | Fix |
| CVE-2021-24347 | High | 8.8 | 54% | - | Fix |
| CVE-2020-12812 | Critical | 9.8 | 49% | KEV + Ransom | Fix |
| CVE-2003-0411 | High | 7.5 | 25% | - | - |
| CVE-2018-9845 | Critical | 9.8 | 13% | - | Fix |
| CVE-2001-0766 | Critical | 9.8 | 8.2% | - | - |
Common questions
How do I fix CVE-2026-59335?
No published fix for CVE-2026-59335 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-59335 being actively exploited?
Not that we know of. CVE-2026-59335 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.30% is the estimated probability that it will be exploited in the next 30 days. That is higher than 22% of all scored CVEs.
How severe is CVE-2026-59335?
CVE-2026-59335 has a CVSS v3 base score of 8.7, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-59335
Markdown
[](https://tridentstack.com/cve/CVE-2026-59335)HTML
<a href="https://tridentstack.com/cve/CVE-2026-59335"><img src="https://tridentstack.com/cve/badge/CVE-2026-59335.svg" alt="CVE-2026-59335"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-28.