CVE-2026-59358: CWE-287: Improper Authentication in Cloud Foundry UAA
Description
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.
CVSS v4.0
Score 7.6high
Affected software
Cloud Foundry
UAA
Cloud Foundry
cf-deployment
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CWE-287) in Cloud Foundry UAA's OAuth token endpoint allows an attacker with a valid user access token to impersonate the client and obtain a client_credentials token with full client privileges. UAA accepts any valid access token whose client_id matches the request as client authentication, without verifying that it is a client credential. A user token obtained via a public authorization_code + PKCE flow can be replayed as Bearer authentication on a client_credentials grant request, resulting in issuance of a new token with full client authorities such as clients.write. This enables creation of arbitrary OAuth clients with attacker-chosen authorities without possessing the client secret. Exploitation requires a non-default client configuration supporting both public user-facing authorization and client_credentials grant types on the same client_id.
Potential Impact
An attacker with a valid user access token for a client configured to support both public authorization and client_credentials grant types can escalate privileges to obtain a fully-privileged client_credentials token. This token grants full client authorities, including the ability to create new OAuth clients with arbitrary permissions. The severity and impact scale with the authorities assigned to the affected client. This could lead to unauthorized creation and management of OAuth clients within the UAA environment.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, review client configurations to avoid enabling both public authorization_code + PKCE flows and client_credentials grant types on the same client_id. Restrict client authorities to the minimum necessary to reduce potential impact. Monitor for unusual client creation activity as a precaution.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-07-04T18:14:46.172Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ac4a0da2cdf04f656898e2f
Added to database: 10/06/2026, 07:18:50 UTC
Last enriched: 10/06/2026, 07:33:12 UTC
Last updated: 10/06/2026, 18:57:28 UTC
Views: 20
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.