Quick answers
- Is CVE-2026-100863 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100863 being exploited in the wild.
- How severe is CVE-2026-100863?
- Medium severity, with a CVSS score of 5, published 27 September 2026.
- Which products and versions are affected?
- Heym 0.0.90 and earlier.
- Is there a fix for CVE-2026-100863?
- A patch was published on 2026-09-27: Version 0.0.91 released with fixes to ssrf_guard.py Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100863 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-100863?
- Check whether you run Heym at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The image-edit loader (_load_image_bytes) fetches caller-controlled HTTP/HTTPS URLs using bare httpx.get with only scheme validation, bypassing the egress-pinning HTTP client used for HTTP nodes. Additionally, _is_public_address fails to validate IPv6 transition forms (NAT64 64:ff9b::/96, IPv4-compatible ::x.x.x.x, 6to4 2002::/16), allowing embedded loopback or RFC1918 addresses to pass both initial validation and dial-time IP pinning. Version 0.0.91 routes image loads through the guarded HTTP client with full address validation and explicit rejection of transition prefixes.
Affected products
- Heym Heym 0.0.90 and earlier
Timeline
- 2026-08-15: disclosed: GitHub Security Advisory GHSA-6rph-qqcv-jqh4 published
- 2026-09-27: patched: Version 0.0.91 released with fixes to ssrf_guard.py