CVE-2026-33992: pyLoad · Server-Side Request Forgery via Download Link Submission Enables Cloud Metadata Exfiltration
Affects pyload-ngSource GCVE Database
Not known to be exploited · CVSS 9.3 Critical.
Data as of 16 Nov 2026, 16:36 UTC
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIpyload-ng | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The recommended remediation is to implement URL validation in the download engine by whitelisting allowed URL schemes (http/https), blocking requests to private IP ranges (RFC 1918, link-local addresses), and blocking access to cloud metadata endpoints such as 169.254.169.254 and metadata.google.internal. Until a patch is released, restrict user access to trusted users only and monitor for suspicious URL submissions.
Description
PyLoad versions up to 0.5.0b3.dev96 contain a Server-Side Request Forgery (SSRF) vulnerability in the download package functionality. Authenticated users can submit arbitrary URLs without validation, allowing requests to internal network services and cloud metadata endpoints. This enables exfiltration of sensitive cloud infrastructure data such as instance IDs, network configuration, authentication keys, SSH keys, and region information. The vulnerability poses a critical risk especially in cloud environments like DigitalOcean, AWS, Google Cloud, and Azure. Exploitation requires a valid PyLoad user account and network access to the PyLoad instance. No official patch link is provided in the data.
References
- github.com/pyload/pyload/security/advisories/GHSA-m74m-f7cr-432x (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-33992 (opens in a new tab)
- github.com/pyload/pyload/commit/b76b6d4ee5e32d2118d26afdee1d0a9e57d4bfe8 (opens in a new tab)
- github.com/pyload/pyload (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/pyload-ng/PYSEC-2026-497.yaml (opens in a new tab)
- pypi.org/project/pyload-ng (opens in a new tab)