# CVE-2026-73530: Flyto2 Core < 2.28.0 SSRF Guard Bypass via is_private_ip()

> Attackers can bypass SSRF protections in Flyto2 Core to access internal IPv6 loopback services via crafted URLs.

- **Severity:** Medium 6.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-35jm-rm2f-hpgj, GHSA-gc4h-hj7x-gp5p

## What is CVE-2026-73530?

CVE-2026-73530 is a medium-severity server-side request forgery vulnerability in flytohub flyto-core, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Flyto2 Core before 2.28.0 contains a server-side request forgery guard bypass vulnerability that allows attackers to reach internal services by supplying URLs using the unblocked IPv6 address `::` which the kernel routes to loopback identically to `0.0.0.0`. Attackers can submit requests or trigger 302 redirects to ` to bypass the private IP range and blocked hostname checks in `is_private_ip()`, reaching services bound to IPv6 loopback across the `http.get`, `http.request`, and `http.batch` modules.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-73530?


## How do I fix CVE-2026-73530?

No fix has been published for CVE-2026-73530 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73530 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73530 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73530 and fix it if it is affected.

What it is: CVE-2026-73530 is a medium-severity server-side request forgery vulnerability in flytohub flyto-core, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73530 exists.

Affected product: flytohub flyto-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73530/ (Markdown: https://insights.sbomify.com/CVE-2026-73530/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73530
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73530
- OSV: https://osv.dev/vulnerability/CVE-2026-73530

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73530/
Summaries are generated and may contain mistakes; the official description above is the record.