CVE-2026-100863 Details
Description
Heym versions 0.0.90 and earlier contain two server-side request forgery (SSRF) egress gaps, both remediated in app/services/ssrf_guard.py in 0.0.91. First, the LLM image-edit input loader (_load_image_bytes) fetched caller-controlled HTTP/HTTPS URLs with a bare httpx.get, applying only a scheme check and bypassing the egress-pinning HTTP client; because the workflow DSL supports "imageInput": "$userInput.body.imageUrl", a webhook or API caller can choose the fetch target when a workflow author uses that expression, allowing requests to loopback, RFC1918, and cloud metadata endpoints. Second, _is_public_address unwrapped only IPv4-mapped IPv6 addresses, so IPv6 transition forms — the NAT64 well-known prefix 64:ff9b::/96, deprecated IPv4-compatible ::x.x.x.x addresses, and 6to4 (2002::/16, classified as globally routable by Python 3.11.0 through 3.11.9) — could carry loopback, RFC1918, link-local, or cloud-metadata IPv4 destinations past both the initial URL validation and the dial-time IP pin. Version 0.0.91 routes the image loader through guard_http_url and the guarded client, evaluates NAT64 and IPv4-compatible addresses by their embedded IPv4 address, and refuses 64:ff9b:1::/48, 6to4, and Teredo (2001::/32) outright.
A server-side request forgery (SSRF) vulnerability has been identified in Heym versions through 0.0.90. This vulnerability arises from two main issues: First, the LLM image-edit input loader (_load_image_bytes) improperly handled HTTP and HTTPS URLs, using a basic httpx.get method that only checked the URL scheme. This flaw allowed webhook or API callers to manipulate the fetch target, potentially accessing loopback, RFC1918, and cloud metadata endpoints. Second, the vulnerability in IPv6 address validation allowed certain transition forms, such as NAT64, deprecated IPv4-compatible addresses, and 6to4, to bypass initial URL checks and dial-time IP pinning, carrying internal IPv4 destinations that could access sensitive metadata.
Users can upgrade to Heym version 0.0.91 or later, which addresses these SSRF vulnerabilities by routing image inputs through a guarded HTTP client that enforces proper URL validation and egress controls. The update also includes enhanced IPv6 address validation, rejecting transition forms that could carry internal destinations.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 27, 2026CISA-ADP
Assessed Sep 30, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-918 | Server-Side Request Forgery (SSRF) | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Heym | <= 0.0.90 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 30, 2026 | CVE Modified | CISA-ADP |
| Sep 27, 2026 | New CVE Received | [email protected] |
Volerion