Cloud Foundry UAA
UAA OAuth Token Endpoint Vulnerability allows user access token reuse for client_credentials grant type
Improper authentication (CWE-287) in the OAuth token endpoint in Cloud Foundry UAA allows a remote, authenticated attacker holding a valid user access token to obtain a fully-privileged client_credentials token for the OAuth client that issued it, by presenting the user token as an OAuth 2.0 Bearer credential on a client_credentials grant request in place of the client’s configured secret. UAA’s client_credentials handling does not verify that the Bearer credential supplied for client authentication is actually a client credential (a client secret or a valid configured client authentication method); it accepts any valid access token whose client_id matches the request. A token obtained by a normal end user through a public authorization_code + PKCE flow — scoped only to uaa.user, carrying a user_id, and recording client_auth_method=none — satisfies this check. That user token cannot itself administer OAuth clients (POST /oauth/clients correctly returns 403), but when replayed as Bearer authentication on a client_credentials request for the same client, UAA issues a new client-only token carrying the client’s full authorities, such as clients.write. An attacker can use that token to create arbitrary new OAuth clients, including clients with attacker-chosen authorities, without ever possessing the client’s actual secret. Exploitation requires a valid user access token (the attacker’s own) for a client that is configured to support both a public, user-facing authorization flow and the client_credentials grant type on the same client_id — a non-default combination. Practical impact scales with the authorities assigned to that client.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.7.0, <= 79.6.0
Fixed in 79.7.0
- <= 60.4.0
Fixed in 60.5.0
Mitigation
Upgrade UAA to 79.7.0 or later.
Upgrade cf-deployment to 60.5.0 or later.
Timeline
Days relative to CVE publicationFirst public PoC 19 h after publication; not in CISA KEV. First PoC: abraxas/CVE-2026-59358 (created 7 Oct 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| abraxas/CVE-2026-59358 | 7 Oct 2026 +19 h | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
PoC characteristics
What to hunt for in your logs · from 1 PoC repoGET /uaa/info
- Ports
- 18258
- PoC User-Agent
evidence_placeholder_removed:false- Seen in
- 1 repo: abraxas/CVE-2026-59358
Regex
Generated from PoC characteristics; not yet reviewed. Matches the request path and query.
(?i)^/uaa/info(?:[?#].*)?$
Suricata
Template generated from PoC characteristics. Review before deploying.
alert http any any -> $HOME_NET [18258] (msg:"GG PoC-Monitor CVE-2026-59358 Cloud Foundry UAA exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/uaa/info"; reference:url,poc.griffinguard.io/cve/CVE-2026-59358; classtype:web-application-attack; sid:9580160; rev:1;)
Sigma
Template generated from PoC characteristics. Review before deploying.
title: Cloud Foundry UAA exploit attempt (CVE-2026-59358)
id: gg-pocmon-cve-2026-59358-9580160
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-59358. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2026-59358
logsource:
category: webserver
detection:
selection:
cs-method: GET
cs-uri-stem|contains|all:
- '/uaa/info'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: high
tags:
- attack.initial_access
- attack.t1190
- cve.2026.59358