CVE-2026-40964
Received Received - Intake
Authentication Bypass in cf-auth-proxy Cloud Foundry

Publication date: 2026-06-01

Last updated on: 2026-06-01

Assigner: VMware

Description
Authentication Bypass in cf-auth-proxy in Cloud Foundry Foundation all installations allows an unauthenticated remote attacker to gain read access to every log and metric for every application and platform component via minting a JWT that the cf-auth-proxy accepts as a valid logs.admin token. Affected versions: - log-cache_release: all versions through v3.2.6 (inclusive); fixed in v3.2.7 or later - CF Deployment: all versions through v55.?.0 (inclusive); fixed in v55.?.0 or later (bundles log-cache_release v3.2.7)
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-01
Last Modified
2026-06-01
Generated
2026-06-02
AI Q&A
2026-06-02
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
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
CWE Icon
KEV
KEV Icon
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
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.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart