SEPTEMBER 17, 2026
Live Feed
Back to database
Case File

CVE-2026-48737

MEDIUM · CVSS 4.9 EPSS 0.18% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-09-15 · Last synced 2026-09-17

CyberRota Analysis

AI-Generated

The vulnerability affects pyLoad versions prior to 0.5.0b3.dev101, allowing low-privileged users to exploit the is_global_address function, which improperly handles IPv6 addresses. This flaw can lead to internal network reconnaissance, potential service disruptions, or exposure of cloud metadata due to misclassification of IPv4 destinations in transition mechanisms like 6to4 or NAT64. Organizations using pyLoad, particularly those relying on affected Python versions, should prioritize upgrading to the fixed version to mitigate these risks.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Detected Signals
exploit

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-48737
Severity
MEDIUM
CVSS
4.9
EPSS
0.18%

Original NVD Description

pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev101, is_global_address in src/pyload/core/utils/web/check.py relies on Python's global-address classification without examining IPv4 destinations embedded in 6to4 or NAT64 IPv6 addresses. A low-privileged user can submit an IPv6 literal through parse_urls to the pre-resolution is_global_host guard. Because host_to_ip is pinned to AF_INET, that guard does not evaluate a hostname's AAAA result. Separately, curl resolves hostnames before the pycurl PREREQFUNC in src/pyload/core/network/http/http_request.py applies the same vulnerable is_global_address check to the actual connection address, so a transition-form AAAA result can be permitted even when it terminates at an embedded loopback, private, CGNAT, or link-local IPv4 address. Exploitation requires the pyLoad host to route the applicable transition mechanism, including 6to4 on affected Python 3.9 through 3.11 deployments or NAT64 on a network with a NAT64 gateway. Successful exploitation can enable internal-network reconnaissance, timing-based confirmation, limited service disruption, or cloud metadata disclosure where the wrapped address is routable. This issue is fixed in version 0.5.0b3.dev101.