Quick answers
- Is CVE-2026-48737 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48737 being exploited in the wild.
- How severe is CVE-2026-48737?
- Medium severity, with a CVSS score of 4.9, published 15 September 2026.
- Which products and versions are affected?
- pyLoad Next Gen <= 0.5.0b3.dev100; pyload-ng (PyPI) <= 0.5.0b3.dev100, ECOSYSTEM:introduced=0,last_affected=0.5.0b3.dev100.
- Is there a fix for CVE-2026-48737?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-48737 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48737?
- Check whether you run pyLoad Next Gen or pyload-ng (PyPI) 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
A Server-Side Request Forgery (SSRF) vulnerability exists in pyLoad due to an incomplete IP address validation logic in the is_global_address function. The application relies on Python's ipaddress.IPv6Address.is_global check, which incorrectly identifies IPv6 transition prefixes (such as 6to4 and NAT64) as globally routable even when they wrap internal IPv4 addresses (e.g., 127.0.0.1 or 169.254.169.254). An attacker with 'Perms.ADD' privileges can provide a specially crafted IPv6 literal or a hostname with a malicious AAAA record to bypass the SSRF guard. This allows the attacker to perform internal network reconnaissance or exfiltrate cloud metadata. The vulnerability is present in pyload-ng up to version 0.5.0b3.dev100.
Affected products
- pyLoad pyload-ng <= 0.5.0b3.dev100
Identifiers
- CVE-2026-48737
- GHSA-m5x5-28jr-gpjj
- PYSEC-2026-2995
Timeline
- 2026-07-08: disclosed
- 2026-07-09: advisory