Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify UAA host and EC signing config
-
DeliveryGET /token_keys unauthenticated
-
ExploitExtract EC private key 'd' parameter
-
ExecutionForge admin-scoped JWT
-
PersistCall privileged CF/UAA APIs
-
ImpactFull platform compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The target must be a Cloud Foundry UAA instance running uaa_release v76.12.0-v78.12.0 (or cf-deployment v30.0.0-v56.0.0) AND configured to use EC (Elliptic Curve) keys for JWT token signing - RSA-signed deployments are not affected, which is a meaningful limiter because RSA is the historical default. Given that precondition, no other special conditions apply: the /token_keys endpoint is unauthenticated and network-reachable by design (CVSS AV:N/AC:L/PR:N/UI:N), so any attacker who can reach the UAA HTTPS port can retrieve the key with one request. No user interaction, no admin role, and no special client are required. |
| Impact | Signals are consistent and severe: CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L describes a network-reachable, no-auth, no-interaction flaw with scope change, which fits exactly - the leaked key compromises every resource server that trusts UAA-signed JWTs, not just UAA itself. No EPSS, KEV, or SSVC data was supplied, and there is no public exploit identified at time of analysis, so we cannot confirm in-the-wild abuse. However, the trigger is a single unauthenticated GET against a well-known endpoint, so the gap between disclosure and mass-scanning is expected to be small; this is a real priority for any operator running an affected version with EC signing keys. The one limiting factor is configuration: deployments still using the default RSA signing keys are not exposed, which materially narrows the affected population compared to the raw 10.0 score. |
| Exploit ScenarioDerived | An unauthenticated attacker on the network discovers an affected UAA instance, issues a single HTTP GET to https://<uaa-host>/token_keys, and parses the returned JWK Set to extract the EC private key's 'd' parameter. Using that private key, the attacker mints a JWT impersonating any user or client (including platform admins) with arbitrary scopes and presents it to any service in the foundation that trusts UAA-signed tokens, achieving full platform compromise. No public exploit identified at time of analysis, but the steps are trivial enough to script in minutes once a vulnerable target is identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 01, 2026
Private key disclosure in Cloud Foundry UAA versions v76.12.0 through v78.12.0 allows unauthenticated remote attackers to retrieve Elliptic Curve (EC) private key material from the public /token_keys endpoint, which is supposed to expose only public verification keys. With the leaked private keys, attackers can forge arbitrary JWTs and impersonate any UAA-authenticated identity across the platform. No public exploit identified at time of analysis, though the CVSS 10.0 score and trivial reproduction step (a single unauthenticated HTTP GET) make weaponization straightforward once the issue is widely known.
RemediationAI
Vendor-released patch: upgrade uaa_release to v78.13.0 or later, or upgrade cf-deployment to v56.1.0 or later (which bundles the fixed UAA), per https://www.cloudfoundry.org/blog/cve-2026-40965-uaa-ec-private-key-disclosure/. Because the private key material has been served publicly for the lifetime of the vulnerable deployment, patching alone is not sufficient: operators must rotate all EC JWT signing keys after upgrading and force re-issuance of outstanding tokens, since any token signed before rotation should be considered forgeable. As an immediate pre-upgrade workaround where rapid patching is not possible, switch UAA's JWT signing configuration from EC to RSA keys (the bug does not affect RSA serialization), accepting the operational cost of a key-type migration and token invalidation; alternatively, restrict network access to the /token_keys endpoint to trusted resource servers only, with the trade-off that any legitimate client relying on dynamic JWKS discovery will break.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
UAA (User Account and Authentication) is the OAuth2/OpenID Connect identity server for Cloud Foundry platforms, issuing and validating JWT access tokens for the entire platform. The /token_keys endpoint follows the JWK Set (RFC 7517) pattern and is intentionally public so that resource servers can fetch the public keys needed to verify JWT signatures. The bug is a CWE-200 (Exposure of Sensitive Information) where UAA's JWK serialization for EC keys incorrectly includes the private 'd' parameter alongside the public 'x' and 'y' coordinates; RSA keys are not affected because their serialization path correctly omits private components. Affected CPEs are cpe:2.3:a:cloud_foundry_foundation:uaa_release and cpe:2.3:a:cloud_foundry_foundation:cf_deployment.
Know when Cf Deployment gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L
Primary rating from Vendor (vmware) · only source for this CVE.
CVSS VectorVendor: vmware
Lifecycle Timeline
1DescriptionCVE.org
Cloud Foundry UAA versions v76.12.0 through v78.12.0 are vulnerable to a private key exposure. The server contains a vulnerability where EC (Elliptic Curve) private keys are inadvertently exposed through the public /token_keys endpoint. This endpoint is designed to provide public key material for JWT token verification but incorrectly exposes private key components for EC keys. The vulnerability affects deployments using EC keys for JWT token signing. The vulnerability does not affect RSA key configurations, only deployments using EC keys for JWT signing.
Affected versions:
- uaa_release: v76.12.0 through v78.12.0 (inclusive); fixed in v78.13.0 or later
- CF Deployment: v30.0.0 through v56.0.0 (inclusive); fixed in v56.1.0 or later (bundles uaa_release v78.13.0)
Executive ViewAI
Cloud Foundry UAA (versions 76.12.0-78.12.0) improperly exposes private encryption keys via an unauthenticated endpoint, allowing attackers to forge authentication credentials and impersonate any user across the platform. No public exploit identified at time of analysis, but the trivial attack vector (unauthenticated HTTP GET) and CVSS 10.0 rating present substantial weaponization risk. Any organization using the affected versions faces immediate risk of account takeover and unauthorized access to all platform resources.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) implement network-level access restrictions on /token_keys endpoint using firewall rules or reverse proxy to limit access to authorized internal services; (2) deploy WAF rules to authenticate and authorize all /token_keys requests; (3) establish continuous monitoring for suspicious JWT tokens with anomalous signatures or claims; (4) audit access logs for unauthenticated /token_keys requests and exploitation patterns; (5) maintain readiness for emergency cryptographic key rotation if compromise is confirmed; (6) implement additional JWT signature verification checks to detect forged authentication tokens.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Cf Deployment
View allCloud Foundry cf-deployment, versions prior to 7.9.0, contain java components that are using an insecure protocol to fet
Adversary-in-the-middle credential theft and privilege escalation affects Cloud Foundry UAA (User Account and Authentica
Privilege escalation in Cloud Foundry UAA (User Account and Authentication server) lets users who authenticate via a fed
Authentication bypass in Cloud Foundry UAA (User Account and Authentication) versions 2.0.0 through 78.13.0 allows remot
Cloud Foundry CAPI (Cloud Controller), versions prior to 1.97.0, when used in a deployment where an app domain is also t
In Cloud Foundry UAA, versions prior to 74.14.0, a CSRF vulnerability exists due to the OAuth2 state parameter not being
Cloud Foundry SMB Volume, versions prior to v2.0.3, accidentally outputs sensitive information to the logs. Rated high s
Cloud Foundry Garden-runC, versions prior to 1.11.0, contains an information exposure vulnerability. Rated high severity
In Cloud Controller versions prior to 1.46.0, cf-deployment versions prior to 1.3.0, and cf-release versions prior to 28
Cloud Foundry Routing, all versions before 0.193.0, does not properly validate nonce input. Rated high severity (CVSS 8.
Privilege escalation in Cloud Foundry smb-volume-release (prior to v3.60.0) and CF Deployment (prior to v56.0.0) lets a
Cloud foundry instances having CAPI version between 1.140 and 1.152.0 along with loggregator-agent v7+ may override othe
EUVD-2026-33817
GHSA-qc5f-2h9q-7m2g
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB