CVE-2026-59388VulnerabilityPublished 30 Oct 2026

Cloud Controller (CAPI) leaks sensitive data into audit logs in multiple instances: custom buildpack credentials are

Source GCVE Database

Compare

Authoritative record:CVE-2026-59388· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to v1.249.0 when convenient.

Data as of 30 Oct 2026, 10:31 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (vmware)	CVSS 3.1	6.5

Patch: Available – fixed in v1.249.0, 60.11.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-8p38-wrq5-f9qc

What to do

Upgrade CAPI (Cloud Foundry Controller) to v1.249.0; cf-deployment to 60.11.0.

Affected software

Product	Affected	Fixed in
Cloud Foundry FoundationCAPI (Cloud Foundry Controller)	Affected <1.249.0	Fixed in v1.249.0
Cloud Foundry Foundationcf-deployment	Affected <60.11.0	Fixed in 60.11.0

AI-suggested

If you cannot patch yet, restrict access to audit logs to trusted personnel only to minimize the risk of credential exposure.

Description

Cloud Controller (CAPI) has multiple instances where sensitive data is leaked into audit logs. Specifically, credentials for custom buildpacks appear in audit events related to app manifest application, creation, and updates. Additionally, syslog drain URL credentials are exposed in user-provided service instance audit events, and service binding parameters are leaked in app manifest and service binding audit events. This exposure could lead to unauthorized access to sensitive credentials if audit logs are accessed by unauthorized parties.

Impact

Confidentiality is impacted due to exposure of sensitive credentials in audit logs. This could allow unauthorized users with access to audit logs to obtain credentials for custom buildpacks, syslog drains, and service bindings. There is no reported impact on integrity or availability. No known exploitation in the wild has been reported.

Summary

The vulnerability in Cloud Controller (CAPI) involves leakage of sensitive credentials into audit logs across several contexts. Custom buildpack credentials are exposed during app manifest operations, syslog drain URL credentials are exposed in user-provided service instance audit events, and service binding parameters are leaked in app manifest and service binding audit events. These leaks occur in audit logs that may be accessible to users or administrators, potentially exposing sensitive information. The CVSS 3.1 score is 6.5, indicating a medium severity with high confidentiality impact but no integrity or availability impact. There is no indication of known exploits in the wild or vendor-provided patches at this time.

References

Community reviews

Loading reviews…