dbcve.org
Cf DeploymentApplication · Cloudfoundry

CVE-2026-22726

MEDIUM · 5.0 CVSS v3.1 Published 2026-05-01
Fix available
A fix is available. Upgrade to 0.372.0 / 55.0.0 or later.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Route Services can be leveraged to send app traffic to network destinations outside of an app's configured egress rules. As a result, a malicious developer with access to Cloudfoundry could configure a route-service that would allow it to send requests to HTTP services on internal networks reachable by the Gorouter, which may not have previously had direct access from outside networks, or from the application. Routing release: affected from v0.118.0 through v0.371.0 (inclusive); upgrade to v0.372.0 or greater. CF Deployment: affected from v0.0.2 through v54.14.0 (inclusive); upgrade to v55.0.0 or greater (includes routing_release v0.372.0).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Route Services in Cloud Foundry can bypass an application's configured egress rules, allowing a malicious developer with CF access to route traffic through the Gorouter to internal network HTTP services that should not be directly accessible from outside networks or from the application itself.

MitigationUpgrade Routing release to v0.372.0 or greater, or CF Deployment to v55.0.0 or greater, to enforce proper egress controls on Route Services.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cf DeploymentApplication
Affected:>= 0.0.2, < 55.0.0
Routing ReleaseApplication
Affected:>= 0.118.0, < 0.372.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed Routing Release version
    Run 'bosh releases | grep routing' or check the Routing Release version deployed in your CF environment
    Affected if The Routing Release version is >= 0.118.0 and < 0.372.0
  2. Check the CF Deployment version
    Run 'bosh releases | grep cf-deployment' or check the cf-deployment release version
    Affected if The CF Deployment version is >= 0.0.2 and < 55.0.0
  3. Determine if Route Services are enabled
    Check the Gorouter configuration for route_services_enabled setting, typically via 'bosh instances' and reviewing the router manifest or via Cloud Foundry API 'cf curl /v2/config'
    Affected if Route Services are enabled in the Gorouter configuration (route_services_enabled is true)
  4. Check for active Route Service bindings
    Query the Cloud Foundry API for route service instances: 'cf curl /v2/service_instances' or review the manifest for any bound route services
    Affected if Any route service instances are bound to application routes in the environment

You are affected if your Routing Release is < 0.372.0 or CF Deployment is < 55.0.0 AND Route Services are enabled and in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.372.0 / 55.0.0 or later
Fixed in 0.372.055.0.0
Interim mitigation

Upgrade Routing release to v0.372.0 or greater, or CF Deployment to v55.0.0 or greater, to enforce proper egress controls on Route Services.

Recommended fix High confidence

Cf Deployment v55.0.0 or Routing Release v0.372.0

  1. Upgrade Cf Deployment to version 55.0.0 or greater, which includes Routing Release v0.372.0 containing the fix
  2. Alternatively, if upgrading Routing Release independently, upgrade to version 0.372.0 or greater
  3. After upgrade, verify route service configurations adhere to intended network policies
Caveat Standard upgrade risks apply; review release notes for changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cf Deployment Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22726 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22726 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data