Medium Integrity

CVE-2026-59357 — Self-UAA OIDC Configuration allows JWT injection to establish unauthorized sessions

Insufficient verification of data authenticity (CWE-345) in the external OIDC login callback in Cloud Foundry UAA v4.5.0 to v79.6.0 (inclusive) allows an authenticated UAA user to bypass the OAuth authorization-code exchange and establish an authenticated external-OIDC browser session, via submitting a UAA access token or a cross-client ID token as the callback’s id_token parameter. The issue only manifests when a UAA zone is configured with an OIDC identity provider whose issuer exactly matches that zone’s own /oauth/token endpoint (a “self-UAA” OIDC configuration). In this configuration, the callback takes a supplied id_token directly instead of requiring the authorization code exchange, and does not verify that the token was actually issued as an ID token for the specific self-OIDC relying-party client. An attacker holding any valid UAA JWT for themselves — including a plain access token with only uaa.user scope, or a valid ID token issued to an unrelated client such as cf — can present it as the callback’s id_token and be authenticated into a mapped local (“shadow”) account. Because the resulting session is not verified against the originating token’s true audience or user_id, its effective privilege depends entirely on the shadow account’s group memberships, which can include administrative scopes such as clients.write. Exploitation requires a valid UAA user JWT, a valid browser login state for the target zone, and the presence of a self-referential OIDC provider configuration — this is not a pre-authentication vulnerability, and does not by itself grant privileges beyond those already held by the mapped shadow account.

Published Oct 6, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: vmware

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.19%

ahead of 8% of scored CVEs · Oct 14, 2026

Affects

Cloud Foundry Foundation

Cf-deployment and 1 more

CVSS base

6.5

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Cloud Foundry Foundation Cf-deployment, Cloud Foundry Foundation UAA).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes matching the vulnerability class (integrity), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Cloud Foundry Foundation	Cf-deployment	≤ 60.4.0	Vulnerable	CVE Program (cve.org) e CISA ADP
Cloud Foundry Foundation	UAA	≥ 4.5.0 and ≤ 79.6.0	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Attack requirements

Present

Privileges required

None

User interaction

Active

Scope

Confidentiality (vulnerable system)

High

Integrity (vulnerable system)

High

Availability (vulnerable system)

None

Confidentiality (subsequent)

None

Integrity (subsequent)

None

Availability (subsequent)

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
6.5	CVSS 4.0	Medium	—	—	security@vmware.com via NIST National Vulnerability Database
6.5	CVSS 4.0	Medium	—	—	vmware via CVE Program (cve.org) e CISA ADP

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

(score shown at the top: security@vmware.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-345 · Insufficient Verification of Data Authenticity

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.19%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Affected products added · cloud foundry/uaa, cloud foundry/cf-deployment
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 6.5
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Awaiting Analysis
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Oct 6, 2026 · vmware

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

www.cloudfoundry.org/blog/cve-2026-59357-self-uaa-oidc-configuration-allows-jwt-injection-
NIST National Vulnerability Database

Elsewhere on this site

Cloud Foundry Foundation
every CVE for this vendor

Integrity
same class

CWE-345
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-59358 UAA OAuth Token Endpoint Vulnerability allows user access token reuse for client_credentials grant type 9d
High CVE-2026-47840 LDAP StartTLS unconditionally disables hostname verification Jul 9, 2026
Critical CVE-2026-41005 UAA accepts SAML Encrypted Assertions authentication bypass Jun 11, 2026
High CVE-2026-40964 Improper Authentication in Cloud Foundry Foundation Log-cache Release Jun 1, 2026
Critical CVE-2026-40965 Exposure of Sensitive Information in Cloud Foundry Foundation Uaa-release Jun 1, 2026
High CVE-2026-41013 Tenant-controlled comma smuggles arbitrary CIFS mount options Jun 1, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-59357 is "Self-UAA OIDC Configuration allows JWT injection to establish unauthorized sessions", rated Medium. It affects Cf-deployment (Cloud Foundry Foundation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.