CVE-2026-73530: Server-Side Request Forgery (SSRF) in flytohub flyto-core
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.
AI Analysis
Technical 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. No official remediation or patch information is currently available.
Potential 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.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, 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.
CVE-2026-73530: Server-Side Request Forgery (SSRF) in flytohub flyto-core
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.
CVSS v4.0
Score 6.3medium
Affected software
flytohub
flyto-core
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
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. No official remediation or patch information is currently available.
Potential 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.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, 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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-12T19:29:19.866Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a7e1a87bf8831d539b1843a
Added to database: 08/13/2026, 19:27:03 UTC
Last enriched: 08/21/2026, 14:05:51 UTC
Last updated: 09/26/2026, 13:47:48 UTC
Views: 62
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.