CVE-2023-34061 is a high severity (CVSS 7.5) denial of service in Cloud Foundry routing release v0.163.0 through v0.283.0. An unauthenticated attacker can force route pruning and degrade availability. Upgrade routing release to v0.284.0 or later, or cf-deployment to v33.6.0 or later.
What's affected
- Cloud Foundry routing release, all versions from v0.163.0 to v0.283.0 inclusive.
- cf-deployment, all versions from v0.28.0 to v33.5.0 inclusive, per the Cloud Foundry advisory.
- Fixed in routing release v0.284.0 and cf-deployment v33.6.0, which includes routing release v0.284.0.
The weakness class is CWE-400, uncontrolled resource consumption. The advisory rates the issue High.
How to check if you're exposed
If you deploy with BOSH, list the routing release version you run:
bosh -d cf releases | grep routing
The deployment name may differ in your environment. To find the cf-deployment version, check the tag or commit you deploy from in your own pipeline repository, or the release notes recorded when you last upgraded.
Compare the result against the ranges above. Also check your monitoring for sudden drops in the number of registered routes, which is the effect the advisory describes.
What to do now
- Plan an upgrade to routing release v0.284.0 or later, or cf-deployment v33.6.0 or later.
- Test the upgrade in a non-production foundation first, and confirm route registration behaves as expected.
- Alert on sharp changes in route counts and on gorouter error rates so you see pruning early.
- Limit which networks can reach the router endpoints that handle registration where your architecture allows.
- Record the deployed versions in your inventory so the next advisory is quick to match.
If you track software dependencies, the free in-browser dependency scan can show which of your components carry known CVEs, and the Gold directory lists the same records in one place.
Why it matters
Cloud Foundry's router keeps a table of routes that map hostnames to application instances. Pruning removes stale entries so traffic does not go to dead backends. The advisory says an attacker without credentials can trigger pruning in a way that removes routes that should stay, so apps become unreachable.
This is a denial of service by exhausting or abusing a bookkeeping mechanism, not by flooding the network. That makes it hard to spot with basic traffic graphs, and route count metrics are a better signal.
The record shows this CVE is not in the CISA Known Exploited Vulnerabilities catalog. The advisory credits two VMware researchers for the report and does not mention exploitation in the wild.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Do I need credentials to be attacked?
No. The advisory says an unauthenticated attacker can force route pruning.
What do I upgrade?
Routing release to v0.284.0 or later, or cf-deployment to v33.6.0 or later. The cf-deployment release includes routing release v0.284.0.
Sources
Last reviewed: 19 October 2026.