Skip to content
Cloud

CVE-2026-59335

8.7
High
EPSS 0.30%Aug 25, 2026

Authenticated user can overwrite UAA JWT key via case-sensitive zone ID mismatch

common questions

Is CVE-2026-59335 being exploited?

Not confirmed. CVE-2026-59335 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-59335?

CVE-2026-59335 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-59335?

Not known from our data. No patch reference has been recorded for CVE-2026-59335, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-59335 affect?

CVE-2026-59335 affects Cloud Foundry UAA (MySQL backend, default collation). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-59335?

Revoke zones.write, avoid MySQL default collation for UAA or move off MySQL, apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Cloud Foundry UAA (MySQL backend, default collation)
impact

Authenticated attacker with zones.write can overwrite system JWT signing key, forge admin JWTs, and fully compromise UAA and trusting Cloud Foundry deployments.

action required

Immediate action required

affected versions
Cloud Foundry cf-deployment
  • affected< 57.0.0
vendor says fixed in57.0.0
Cloud Foundry UAA
  • affected< 78.16.0
vendor says fixed in78.16.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free