VulnerabilityPublished 30 Apr 2026

CVE-2026-22726: CloudFoundry Foundation Routing release · Improper Restriction of Communication Channel to Intended Endpoints

Affects CloudFoundry Foundation Routing releaseSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.0 Medium : upgrade to v0.372.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in v0.372.0, v55.0.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Routing release to v0.372.0; CF Deployment to v55.0.0.

Affected software

Product	Affected	Fixed in
CloudFoundry FoundationRouting release	Affected >=0.118.0 <0.372.0	Fixed in v0.372.0
CloudFoundry FoundationCF Deployment	Affected >=0.0.2 <55.0.0	Fixed in v55.0.0

AI-suggested

A fix is available by upgrading to Routing release version v0.372.0 or greater and CF Deployment version v55.0.0 or greater, which include the necessary remediation. Since the vendor advisory indicates these versions address the issue, applying these upgrades is the recommended mitigation. Patch status is confirmed by the vendor's version guidance. No additional mitigation steps are indicated.

Description

CVE-2026-22726 is a medium severity vulnerability in the CloudFoundry Foundation Routing release that allows a malicious developer to configure route services to send application traffic to network destinations outside of the app's configured egress rules. This improper restriction of communication channels can enable access to internal HTTP services reachable by the Gorouter that were not previously accessible from outside networks or the application itself. The vulnerability affects Routing release versions from v0.118.0 through v0.371.0 and CF Deployment versions from v0.0.2 through v54.14.

Impact

The vulnerability allows a malicious developer to bypass configured egress restrictions by leveraging route services to send traffic to internal HTTP services accessible via the Gorouter. This could lead to unintended network communication and potential disruption of availability (as indicated by the CVSS vector showing impact on availability). There is no direct impact on confidentiality or integrity reported. No known exploits have been observed in the wild.

CWE-923Improper Restriction of Communication Channel to Intended Endpoints (opens in a new tab)
Class weakness
The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.1 (opens in a new tab)
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
Attack patterns
Contradictory Destinations in Traffic Routing Schemes (opens in a new tab)
Android Activity Hijack (opens in a new tab)
DHCP Spoofing (opens in a new tab)
Infrastructure Manipulation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

cloudfoundry.org/blog/cve-2026-22726-route-services-firewall-bypass/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 May 2026, 02:15 UTC

WeaknessesCWE-923

Technical details

References

Community reviews

Related threats