Is CVE-2026-59388 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-59388 being exploited in the wild.

How severe is CVE-2026-59388?

Medium severity, with a CVSS score of 6.5, published 30 October 2026.

Which products and versions are affected?

Cloud Foundry Foundation Cf-Deployment before v60.11.0; Cloud Foundry Foundation Cloud Controller (CAPI) up to v1.248.0.

Is there a fix for CVE-2026-59388?

Yes: fixed in CAPI v1.249.0 or greater; cf-deployment v60.11.0 or greater. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-59388 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-59388?

Check whether you run Cloud Foundry Foundation Cf-Deployment or Cloud Foundry Foundation Cloud Controller (CAPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-59388: Cloud Foundry Cloud Controller credential exposure in audit logs

CVE-2026-59388 · Severity: medium · CVSS 6.5 · Published 2026-10-30

Cloud Foundry's Cloud Controller (CAPI), which manages application deployments and services, leaks sensitive credentials into audit logs where they can be accessed by users with audit log permissions. Exposed secrets include custom buildpack credentials, syslog drain URLs, and service binding parameters, which could allow attackers or authorized users to gain unauthorized access to integrated services and infrastructure.

Technologies: Cloud Foundry Foundation Cf-Deployment. Vendors: Cloud Foundry Foundation.

Quick answers

Is CVE-2026-59388 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-59388 being exploited in the wild.
How severe is CVE-2026-59388?: Medium severity, with a CVSS score of 6.5, published 30 October 2026.
Which products and versions are affected?: Cloud Foundry Foundation Cf-Deployment before v60.11.0; Cloud Foundry Foundation Cloud Controller (CAPI) up to v1.248.0.
Is there a fix for CVE-2026-59388?: Yes: fixed in CAPI v1.249.0 or greater; cf-deployment v60.11.0 or greater. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-59388 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-59388?: Check whether you run Cloud Foundry Foundation Cf-Deployment or Cloud Foundry Foundation Cloud Controller (CAPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: CAPI v1.249.0 or greater; cf-deployment v60.11.0 or greater

Technical details

The Cloud Controller fails to redact sensitive data before writing audit events, exposing buildpack credentials in app manifest/create/update events, syslog drain URL credentials in user-provided service instance events, and service binding parameters in manifest and binding events. The vulnerability requires authentication and network access to view audit logs. An attacker with audit log access can extract credentials to compromise connected services.

Affected products

Cloud Foundry Foundation Cloud Controller (CAPI) up to v1.248.0
Cloud Foundry Foundation cf-deployment before v60.11.0

Timeline

2026-10-20: disclosed

References

https://www.cloudfoundry.org/blog/cve-2026-59388-cloud-controller-exposes-secrets-in-audit-log/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.