CVE-2026-40964
Authentication Bypass in cf-auth-proxy Cloud Foundry
Publication date: 2026-06-01
Last updated on: 2026-06-01
Assigner: VMware
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| cloud_foundry_foundation | log_cache_release | to 3.2.6 (inc) |
| cloud_foundry_foundation | cf_deployment | to 55.?.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-287 | When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows an unauthenticated remote attacker to gain read access to every log and metric for every application and platform component by bypassing authentication in cf-auth-proxy. Such unauthorized access to sensitive logs and metrics could potentially lead to exposure of personal or sensitive data.
Unauthorized access to logs and metrics may violate data protection and privacy requirements under regulations like GDPR and HIPAA, which mandate strict controls over access to personal and sensitive information.
Therefore, this vulnerability could negatively impact compliance with these common standards and regulations by enabling unauthorized data access.
Can you explain this vulnerability to me?
This vulnerability is an authentication bypass in the cf-auth-proxy component of Cloud Foundry Foundation. It allows an unauthenticated remote attacker to gain read access to all logs and metrics for every application and platform component. The attacker achieves this by minting a JSON Web Token (JWT) that the cf-auth-proxy mistakenly accepts as a valid logs.admin token.
How can this vulnerability impact me? :
The impact of this vulnerability is that an attacker without any authentication can read sensitive logs and metrics across all applications and platform components. This could lead to exposure of sensitive information contained in logs, potentially aiding further attacks or data leakage.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade affected components to fixed versions.
- Upgrade log-cache_release to version 3.2.7 or later.
- Upgrade CF Deployment to version v55.?.0 or later, which bundles log-cache_release v3.2.7.