CVE-2026-59357 (GCVE-0-2026-59357)
Vulnerability from cvelistv5
Published
2026-10-06 07:06
Modified
2026-10-06 11:49
Severity ?
VLAI Severity ?
EPSS score ?
CWE
- CWE-345 - Insufficient Verification of Data Authenticity
Summary
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.
References
Impacted products
| Vendor | Product | Version | |||||||
|---|---|---|---|---|---|---|---|---|---|
| Cloud Foundry | UAA |
Version: 4.5.0 ≤ 79.6.0 |
|||||||
|
|||||||||
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-59357",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-06T11:47:58.110314Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-06T11:49:21.187Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "UAA",
"repo": "https://github.com/cloudfoundry/uaa",
"vendor": "Cloud Foundry",
"versions": [
{
"lessThanOrEqual": "79.6.0",
"status": "affected",
"version": "4.5.0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "79.7.0",
"versionType": "semver"
}
]
},
{
"product": "cf-deployment",
"repo": "https://github.com/cloudfoundry/cf-deployment",
"vendor": "Cloud Foundry",
"versions": [
{
"lessThanOrEqual": "60.4.0",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "60.5.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eInsufficient 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\u2019s id_token parameter.\u003c/p\u003e\u003cp\u003eThe issue only manifests when a UAA zone is configured with an OIDC identity provider whose issuer exactly matches that zone\u2019s own /oauth/token endpoint (a \u201cself-UAA\u201d 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 \u2014 including a plain access token with only uaa.user scope, or a valid ID token issued to an unrelated client such as cf \u2014 can present it as the callback\u2019s id_token and be authenticated into a mapped local (\u201cshadow\u201d) account. Because the resulting session is not verified against the originating token\u2019s true audience or user_id, its effective privilege depends entirely on the shadow account\u2019s group memberships, which can include administrative scopes such as clients.write.\u003c/p\u003e\u003cp\u003eExploitation 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 \u2014 this is not a pre-authentication vulnerability, and does not by itself grant privileges beyond those already held by the mapped shadow account.\u003c/p\u003e"
}
],
"value": "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\u2019s id_token parameter.\n\n\n\nThe issue only manifests when a UAA zone is configured with an OIDC identity provider whose issuer exactly matches that zone\u2019s own /oauth/token endpoint (a \u201cself-UAA\u201d 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 \u2014 including a plain access token with only uaa.user scope, or a valid ID token issued to an unrelated client such as cf \u2014 can present it as the callback\u2019s id_token and be authenticated into a mapped local (\u201cshadow\u201d) account. Because the resulting session is not verified against the originating token\u2019s true audience or user_id, its effective privilege depends entirely on the shadow account\u2019s group memberships, which can include administrative scopes such as clients.write.\n\n\n\nExploitation 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 \u2014 this is not a pre-authentication vulnerability, and does not by itself grant privileges beyond those already held by the mapped shadow account."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"exploitMaturity": "PROOF_OF_CONCEPT",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "ACTIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "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",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-345",
"description": "CWE-345: Insufficient Verification of Data Authenticity",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-06T07:06:18.486Z",
"orgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d",
"shortName": "vmware"
},
"references": [
{
"url": "https://www.cloudfoundry.org/blog/cve-2026-59357-self-uaa-oidc-configuration-allows-jwt-injection-to-establish-unauthorized-sessions/"
}
],
"title": "Self-UAA OIDC Configuration allows JWT injection to establish unauthorized sessions"
}
},
"cveMetadata": {
"assignerOrgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d",
"assignerShortName": "vmware",
"cveId": "CVE-2026-59357",
"datePublished": "2026-10-06T07:06:18.486Z",
"dateReserved": "2026-07-04T18:14:46.172Z",
"dateUpdated": "2026-10-06T11:49:21.187Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-59357\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-10-06T11:47:58.110314Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-10-06T11:49:16.355Z\"}}], \"cna\": {\"title\": \"Self-UAA OIDC Configuration allows JWT injection to establish unauthorized sessions\", \"metrics\": [{\"format\": \"CVSS\", \"cvssV4_0\": {\"Safety\": \"NOT_DEFINED\", \"version\": \"4.0\", \"Recovery\": \"NOT_DEFINED\", \"baseScore\": 6.5, \"Automatable\": \"NOT_DEFINED\", \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"valueDensity\": \"NOT_DEFINED\", \"vectorString\": \"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\", \"exploitMaturity\": \"PROOF_OF_CONCEPT\", \"providerUrgency\": \"NOT_DEFINED\", \"userInteraction\": \"ACTIVE\", \"attackComplexity\": \"LOW\", \"attackRequirements\": \"PRESENT\", \"privilegesRequired\": \"NONE\", \"subIntegrityImpact\": \"NONE\", \"vulnIntegrityImpact\": \"HIGH\", \"subAvailabilityImpact\": \"NONE\", \"vulnAvailabilityImpact\": \"NONE\", \"subConfidentialityImpact\": \"NONE\", \"vulnConfidentialityImpact\": \"HIGH\", \"vulnerabilityResponseEffort\": \"NOT_DEFINED\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"repo\": \"https://github.com/cloudfoundry/uaa\", \"vendor\": \"Cloud Foundry\", \"product\": \"UAA\", \"versions\": [{\"status\": \"affected\", \"version\": \"4.5.0\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"79.6.0\"}, {\"status\": \"unaffected\", \"version\": \"79.7.0\", \"versionType\": \"semver\"}]}, {\"repo\": \"https://github.com/cloudfoundry/cf-deployment\", \"vendor\": \"Cloud Foundry\", \"product\": \"cf-deployment\", \"versions\": [{\"status\": \"affected\", \"version\": \"0\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"60.4.0\"}, {\"status\": \"unaffected\", \"version\": \"60.5.0\", \"versionType\": \"semver\"}]}], \"references\": [{\"url\": \"https://www.cloudfoundry.org/blog/cve-2026-59357-self-uaa-oidc-configuration-allows-jwt-injection-to-establish-unauthorized-sessions/\"}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"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\\u2019s id_token parameter.\\n\\n\\n\\nThe issue only manifests when a UAA zone is configured with an OIDC identity provider whose issuer exactly matches that zone\\u2019s own /oauth/token endpoint (a \\u201cself-UAA\\u201d 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 \\u2014 including a plain access token with only uaa.user scope, or a valid ID token issued to an unrelated client such as cf \\u2014 can present it as the callback\\u2019s id_token and be authenticated into a mapped local (\\u201cshadow\\u201d) account. Because the resulting session is not verified against the originating token\\u2019s true audience or user_id, its effective privilege depends entirely on the shadow account\\u2019s group memberships, which can include administrative scopes such as clients.write.\\n\\n\\n\\nExploitation 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 \\u2014 this is not a pre-authentication vulnerability, and does not by itself grant privileges beyond those already held by the mapped shadow account.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eInsufficient 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\\u2019s id_token parameter.\u003c/p\u003e\u003cp\u003eThe issue only manifests when a UAA zone is configured with an OIDC identity provider whose issuer exactly matches that zone\\u2019s own /oauth/token endpoint (a \\u201cself-UAA\\u201d 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 \\u2014 including a plain access token with only uaa.user scope, or a valid ID token issued to an unrelated client such as cf \\u2014 can present it as the callback\\u2019s id_token and be authenticated into a mapped local (\\u201cshadow\\u201d) account. Because the resulting session is not verified against the originating token\\u2019s true audience or user_id, its effective privilege depends entirely on the shadow account\\u2019s group memberships, which can include administrative scopes such as clients.write.\u003c/p\u003e\u003cp\u003eExploitation 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 \\u2014 this is not a pre-authentication vulnerability, and does not by itself grant privileges beyond those already held by the mapped shadow account.\u003c/p\u003e\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-345\", \"description\": \"CWE-345: Insufficient Verification of Data Authenticity\"}]}], \"providerMetadata\": {\"orgId\": \"dcf2e128-44bd-42ed-91e8-88f912c1401d\", \"shortName\": \"vmware\", \"dateUpdated\": \"2026-10-06T07:06:18.486Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2026-59357\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-10-06T11:49:21.187Z\", \"dateReserved\": \"2026-07-04T18:14:46.172Z\", \"assignerOrgId\": \"dcf2e128-44bd-42ed-91e8-88f912c1401d\", \"datePublished\": \"2026-10-06T07:06:18.486Z\", \"assignerShortName\": \"vmware\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…