{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-22726 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-22726 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22726 is a medium-severity server-side request forgery vulnerability in CloudFoundry Foundation CF Deployment, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-22726 and fix it if it is affected.\n\nWhat it is: CVE-2026-22726 is a medium-severity server-side request forgery vulnerability in CloudFoundry Foundation CF Deployment, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-22726 in the wild and no public exploit code.\n\nAffected product: CloudFoundry Foundation CF Deployment. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-22726/ (Markdown: https://insights.sbomify.com/CVE-2026-22726/index.md)","id":"CVE-2026-22726","markdown":"https://insights.sbomify.com/CVE-2026-22726/index.md","name":"CVE-2026-22726","record":{"aliases":["GHSA-rmvv-67vj-q642"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"CloudFoundry routing","requires_auth":"low_privilege","summary":"Malicious developers can bypass egress rules to access internal network services via route services, requiring an upgrade to the routing release.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"cf-deployment","vendor":"cloudfoundry"},{"product":"routing_release","vendor":"cloudfoundry"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-923","name":"Improper Restriction of Communication Channel to Intended Endpoints"}],"description":"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.\nRouting 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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Route Services Firewall Bypass","id":"CVE-2026-22726","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Cloud Foundry unprotected internal endpoints","id":"CVE-2026-22727"},"packages":[],"prev":{"headline":"UAA User Token Revocation logic error","id":"CVE-2026-22723"},"products":["CF Deployment","Routing release"],"published":"2026-04-30","related":[{"cvss_score":9.1,"headline":"Auth bypass in Cloud Foundry Diego and CF Deployment","id":"CVE-2022-31733","kev_date_added":null,"published":"2023-02-03"},{"cvss_score":8.8,"headline":"UAA fails to check the state parameter when authenticating with external IDPs","id":"CVE-2020-5402","kev_date_added":null,"published":"2020-02-27"},{"cvss_score":8.8,"headline":"UAA logs all query parameters with debug logging level","id":"CVE-2019-11293","kev_date_added":null,"published":"2019-12-06"},{"cvss_score":8.8,"headline":"Cloud Foundry UAA logs query parameters in tomcat access file","id":"CVE-2019-11290","kev_date_added":null,"published":"2019-11-25"},{"cvss_score":8.8,"headline":"Password leak in smbdriver logs","id":"CVE-2019-11283","kev_date_added":null,"published":"2019-10-23"},{"cvss_score":8.8,"headline":"Information disclosure in Garden-runC","id":"CVE-2018-1191","kev_date_added":null,"published":"2018-03-29"},{"cvss_score":8.7,"headline":"Java Projects using HTTP to fetch dependencies","id":"CVE-2019-3801","kev_date_added":null,"published":"2019-04-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-01","vendors":["CloudFoundry Foundation"]},"summary":"Malicious developers can bypass egress rules to access internal network services via route services, requiring an upgrade to the routing release.","url":"https://insights.sbomify.com/CVE-2026-22726/"}