VulnerabilityPublished 13 Aug 2026

CVE-2026-73530: flytohub flyto-core · Server-Side Request Forgery (SSRF)

Affects flytohub flyto-coreSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.28.0 when convenient.

Data as of 11 Nov 2026, 23:24 UTC

CVSS 4.0 base score

6.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.28.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: High
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: High: There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Aug 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 11 Nov 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 flytohub flyto-core to 2.28.0.

Affected software

Product	Affected	Fixed in
flytohubflyto-core	Affected <2.28.0	Fixed in–
GitHubflyto-core`pkg:github/flyto-core`Other threats	Affected <2.28.0	Fixed in 2.28.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should consider restricting or monitoring usage of the http.get, http.request, and http.batch modules for requests involving IPv6 loopback addresses. Avoid relying solely on is_private_ip() for SSRF protection against IPv6 loopback addresses. Follow vendor updates closely for an official patch or mitigation.

Description

Flyto2 Core versions prior to 2.28.0 contain a server-side request forgery (SSRF) vulnerability. This flaw allows attackers to bypass SSRF protections by using the IPv6 address ::, which the kernel routes to the loopback interface similarly to 0.0.0.0. By exploiting this, attackers can reach internal services that should be protected by private IP and hostname checks in the is_private_ip() function. The vulnerability affects the http.get, http.request, and http.batch modules. The issue is identified with a CVSS 4.0 score of 6.3, indicating medium severity.

Impact

An attacker with low privileges can exploit this vulnerability to bypass SSRF protections and access internal services bound to the IPv6 loopback interface. This could lead to unauthorized internal network access, potentially exposing sensitive internal resources or services that are otherwise protected by private IP and hostname checks. The CVSS 4.0 base score is 6.3, reflecting a medium severity impact without requiring user interaction or elevated privileges beyond low privileges.

Summary

CVE-2026-73530 is an SSRF vulnerability in flytohub's flyto-core product before version 2.28.0. The vulnerability arises because the SSRF guard does not block requests using the IPv6 address ::, which the kernel treats as loopback, effectively bypassing private IP range and hostname checks implemented in the is_private_ip() function. This allows attackers to submit requests or trigger 302 redirects to internal services bound to the IPv6 loopback interface via the http.get, http.request, and http.batch modules.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Aug 2026, 14:05 UTC

Technical details

References

Community reviews

Related threats