Is CVE-2026-59387 exploited in the wild?

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

How severe is CVE-2026-59387?

High severity, with a CVSS score of 8.8, published 30 October 2026.

Which products and versions are affected?

Cloud Foundry Foundation CAPI (Cloud Controller) up to v1.245.0; Cloud Foundry Foundation Cf-Deployment prior to v60.7.0.

Is there a fix for CVE-2026-59387?

Yes: fixed in CAPI v1.246.0 or greater; CF Deployment v60.7.0 or greater (includes CAPI v1.247.0). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-59387 attacked?

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

Am I affected by CVE-2026-59387?

Check whether you run Cloud Foundry Foundation CAPI (Cloud Controller) or Cloud Foundry Foundation Cf-Deployment 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-59387: Cloud Foundry CAPI broken access control in /internal/v3/ endpoints

CVE-2026-59387 · Severity: high · CVSS 8.8 · Published 2026-10-30

Cloud Foundry's CAPI (Cloud Controller) is the core API that manages application deployment in cloud platforms. An attacker with a valid application GUID can bypass authentication protections and forge staging callbacks to modify application state and metadata, allowing privilege escalation beyond their assigned role. This could lead to unauthorized changes to deployed applications and exposure of sensitive deployment information.

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

Quick answers

Is CVE-2026-59387 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-59387 being exploited in the wild.
How severe is CVE-2026-59387?: High severity, with a CVSS score of 8.8, published 30 October 2026.
Which products and versions are affected?: Cloud Foundry Foundation CAPI (Cloud Controller) up to v1.245.0; Cloud Foundry Foundation Cf-Deployment prior to v60.7.0.
Is there a fix for CVE-2026-59387?: Yes: fixed in CAPI v1.246.0 or greater; CF Deployment v60.7.0 or greater (includes CAPI v1.247.0). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-59387 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-59387?: Check whether you run Cloud Foundry Foundation CAPI (Cloud Controller) or Cloud Foundry Foundation Cf-Deployment 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.246.0 or greater; CF Deployment v60.7.0 or greater (includes CAPI v1.247.0)

Technical details

The Nginx routing configuration for Cloud Controller blocks unauthenticated access to /internal/v4/ and /internal/v5/ endpoints but fails to apply equivalent protections to /internal/v3/ staging callback endpoints. An attacker with knowledge of a valid droplet or build GUID can submit a forged staging callback via /internal/v3/staging/:guid/droplet_completed or /internal/v3/staging/:guid/build_completed without OAuth or mTLS authentication, allowing arbitrary process metadata and sidecar data injection. A SpaceAuditor role can enumerate GUIDs without write permissions, enabling effective privilege escalation.

Affected products

Cloud Foundry Foundation CAPI (Cloud Controller) up to v1.245.0
Cloud Foundry Foundation CF Deployment prior to v60.7.0

Timeline

2026-10-20: disclosed: Initial vulnerability report published
2026-10-30: advisory

References

https://www.cloudfoundry.org/blog/cve-2026-59387-broken-access-control-restriction-in-cloud-controller-api/

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