How severe is GHSA-gc4h-hj7x-gp5p?

No CVSS score has been assigned to GHSA-gc4h-hj7x-gp5p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gc4h-hj7x-gp5p?

Affected package information for GHSA-gc4h-hj7x-gp5p is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-gc4h-hj7x-gp5p?

Upgrade the affected component to the fixed release for GHSA-gc4h-hj7x-gp5p, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect GHSA-gc4h-hj7x-gp5p in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`). Because exploitation targets the running service rather than your application code, O3 also flags the exploit behaviour from runtime telemetry and egress traffic.

How do I mitigate GHSA-gc4h-hj7x-gp5p if there is no patch (or I can't update yet)?

Reduce reachability while you patch: restrict network access to the service to trusted sources, disable or gate the affected component where your deployment allows it, and add a WAF/IPS signature if one exists for GHSA-gc4h-hj7x-gp5p. O3's runtime protection blocks the server-side request forgery (ssrf) flaw at execution, which holds the line on hosts you cannot patch immediately.

How does O3 Security protect against GHSA-gc4h-hj7x-gp5p?

O3 detects and blocks GHSA-gc4h-hj7x-gp5p exploitation at runtime with eBPF exploit-chain detection, plus L7 egress monitoring that catches a post-exploitation callback and cuts the attacker's outbound channel.

Is GHSA-gc4h-hj7x-gp5p actively exploited in the wild?

No public exploit code has been indexed for GHSA-gc4h-hj7x-gp5p yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-gc4h-hj7x-gp5p?

GHSA-gc4h-hj7x-gp5p has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 34th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-gc4h-hj7x-gp5p?

GHSA-gc4h-hj7x-gp5p is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-gc4h-hj7x-gp5p published, and has it been updated?

GHSA-gc4h-hj7x-gp5p was published on August 13, 2026 and was last updated on September 11, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

GHSA-gc4h-hj7x-gp5p — Flytohub

GHSA-gc4h-hj7x-gp5p is a Server-Side Request Forgery (SSRF) vulnerability. A fix is available — see the affected versions and patch details below.

Flyto2 Core < 2.28.0 SSRF Guard Bypass via is_private_ip()

Published

Aug 13, 2026

Updated

Sep 11, 2026

Affected

14 versions

Patched

See advisory

Exploits

None indexed

Exploitation data as of Sep 17, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-gc4h-hj7x-gp5p.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs34th percentile — riskier than 34% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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 inis_private_ip(), reaching services bound to IPv6 loopback across the http.get, http.request, and http.batch` modules.

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`). Because exploitation targets the running service rather than your application code, O3 also flags the exploit behaviour from runtime telemetry and egress traffic.
Fix
Upgrade the affected component to the fixed release for GHSA-gc4h-hj7x-gp5p, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
Reduce reachability while you patch: restrict network access to the service to trusted sources, disable or gate the affected component where your deployment allows it, and add a WAF/IPS signature if one exists for GHSA-gc4h-hj7x-gp5p. O3's runtime protection blocks the server-side request forgery (ssrf) flaw at execution, which holds the line on hosts you cannot patch immediately.
How O3 protects you
O3 detects and blocks GHSA-gc4h-hj7x-gp5p exploitation at runtime with eBPF exploit-chain detection, plus L7 egress monitoring that catches a post-exploitation callback and cuts the attacker's outbound channel.

Tailored to GHSA-gc4h-hj7x-gp5p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-gc4h-hj7x-gp5p in your dependencies?

O3 Security finds GHSA-gc4h-hj7x-gp5p across dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works