CVE-2026-59396

DoS Vulnerability in UAA Related to JWKS URI Handling

Published Oct 30, 2026 CVSS 4.0 · 6.9 Medium EPSS < 1% KEV · Not listed
Description
A denial-of-service vulnerability exists in UAA's private_key_jwt client-authentication mechanism. When UAA retrieves a remote JWKS URI, it caches the response. Invalid authentication attempts can trigger full deserialization of this cached data. An attacker with prerequisites (write access to clients or a compromised endpoint) can send anonymous requests that force repeated parsing of large cached objects, causing excessive CPU usage and potential Java heap exhaustion via OutOfMemoryError, resulting in service unavailability.

Analysis

AI-generated

Technical impact

A DoS vulnerability exists in Cloud Foundry UAA’s private_key_jwt client‑authentication path. When UAA retrieves a JWKS document from a remote URI it stores the response in a cache. Subsequent authentication attempts trigger full deserialization of this cached data. If an attacker can influence the JWKS content—by writing client configuration or compromising an endpoint—it can cause repeated parsing of large, complex objects. The resulting CPU exhaustion and OutOfMemoryError can deplete the Java heap and render the UAA service unavailable to legitimate users.

Affected Systems

Cloud Foundry UAA and cf‑deployment are affected. No specific impacted versions are listed; the vulnerability applies to any deployment using the insecure JWKS URI handling mechanism described.

Risk and Exploitability

The CVSS score is 6.9, indicating a moderate impact. EPSS score is not available and the issue is not in the CISA KEV catalog. The attack vector is inferred to be remote, requiring the attacker to send crafted anonymous requests to the UAA instance. Successful exploitation would lead to service unavailability due to excessive resource consumption and potential heap exhaustion.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to the latest Cloud Foundry UAA release that addresses the JWKS URI handling flaw.
  • Configure the application to limit the size of cached JWKS responses or disable caching for external JWKS URIs.
  • Implement monitoring for CPU and memory usage to detect potential OutOfMemoryError incidents early.

Generated by OpenCVE AI on October 30, 2026 at 09:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Cloudfoundry
Cloudfoundry cf-deployment
Cloudfoundry uaa
Vendors & Products Cloudfoundry
Cloudfoundry cf-deployment
Cloudfoundry uaa
Type Values Removed Values Added
Weaknesses CWE-400
CWE-502
Type Values Removed Values Added
Description A denial-of-service vulnerability exists in UAA's private_key_jwt client-authentication mechanism. When UAA retrieves a remote JWKS URI, it caches the response. Invalid authentication attempts can trigger full deserialization of this cached data. An attacker with prerequisites (write access to clients or a compromised endpoint) can send anonymous requests that force repeated parsing of large cached objects, causing excessive CPU usage and potential Java heap exhaustion via OutOfMemoryError, resulting in service unavailability.
Title DoS Vulnerability in UAA Related to JWKS URI Handling
References
Metrics cvssV3_1

{'score': 4.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H'}

cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Oct 30, 2026, 8:10 PM
Reserved
Jul 4, 2026, 6:15 PM
Status
Awaiting Analysis
Published
Oct 30, 2026, 9:17 AM
Modified
Oct 30, 2026, 8:17 PM