Broken access control restriction in Cloud Controller API
Impact
Cloud Controller API versions before v1.247.0 and cf-deployment versions before 60.7.0 have a broken access control restriction, allowing attackers with a valid build or droplet GUID to submit forged staging callbacks and escalate privileges. The weakness is due to a missing deny rule for /internal/v3/ endpoints. An attacker can exploit this without OAuth or mutual TLS.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
Cloud Foundry · vmware
CAPI (Cloud Controller API)
1 range
Cloud Foundry · vmware
CAPI (Cloud Controller API)
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → before v1.247.0
semver versions
Other versions: unknown
Cloud Foundry · vmware
cf-deployment
1 range
Cloud Foundry · vmware
cf-deployment
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → before 60.7.0
semver versions
Other versions: unknown
Original source description
The Nginx routing configuration for Cloud Controller blocks unauthenticated access to /internal/v4/ and /internal/v5/ endpoints but omits an equivalent deny rule for /internal/v3/. As a result, the staging callback endpoints /internal/v3/staging/:guid/droplet_completed and /internal/v3/staging/:guid/build_completed are reachable from the public API listener without OAuth or mutual TLS.
An attacker with a valid build or droplet GUID can submit a forged staging callback, transition a droplet to STAGED, and persist arbitrary process metadata and sidecar data with no associated package or actor. A SpaceAuditor can enumerate GUIDs without write permissions, making this an effective privilege escalation beyond the intended role boundary.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-59387View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changes- CVE · CVE-2026-59387
Observed 2026-10-30T20:23:54.922Z · upstream updated 2026-10-30T20:10:53.458Z
Weakness classification changed
before
[]
after
[ { "id": "CWE-284", "description": "CWE-284 Improper Access Control", "source": "CISA-ADP" } ] - CVE · CVE-2026-59387
Observed 2026-10-30T17:16:48.524Z · upstream updated 2026-10-30T15:47:46.591Z
Prioritization updated
before
[]
after
[ { "source": "CISA-ADP", "type": "SSVC", "role": "CISA Coordinator", "timestamp": "2026-10-30T15:27:30.662530Z", "decisions": [ { "name": "Exploitation", "value": "none" }, { "name": "Automatable", "value": "no" }, { "name": "Technical Impact", "value": "total" } ] } ]
Large field values are marked as truncated previews. Original source snapshots remain retained.
Showing up to 50 most recent observed changes.