pyLoad: SSRF filter bypass via HTTP redirect in BaseDownloader (Incomplete fix for CVE-2026-33992)
CVE-2026-35459GHSA-7gvf-3w72-p2pg
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI pyload-ng
- Affected
- <= 0.5.0b3.dev96
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-7gvf-3w72-p2pg lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev96
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-7gvf-3w72-p2pg lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev96
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N · score source
- EPSS
- CVE-2026-35459: 0.28% estimated exploitation activity in the next 30 days; percentile 21.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary The fix for CVE-2026-33992 (GHSA-m74m-f7cr-432x) added IP validation to BaseDownloader.download() that checks the hostname of the initial download URL. However, pycurl is configured with FOLLOWLOCATION=1 and MAXREDIRS=10, causing it to automatically follow HTTP redirects. Redirect targets are never validated against the SSRF filter. An authenticated user with ADD permission can bypass the SSRF fix by submitting a URL that redirects to an internal address. Root Cause The SSRF check at src/pyload/plugins/base/downloader.py:335-341 validates only the initial URL: dlhostname = urllib.parse.urlparse(dlurl).hostname if isipaddress(dlhostname) and not isglobaladdress(dlhostname): self.fail(...) else: for ip in hosttoip(dlhostname): if not isglobaladdress(ip): self.fail(...) After the check passes, download() is called. pycurl is configured at src/pyload/core/network/http/httprequest.py:114-115 to follow redirects: self.c.setopt(pycurl.FOLLOWLOCATION, 1)…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-7gvf-3w72-p2pg
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-7gvf-3w72-p2pg
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-35459 Advisory: pyLoad: SSRF filter bypass via HTTP redirect in BaseDownloader (Incomplete fix for CVE-2026-33992) IDs: CVE-2026-35459, GHSA-7gvf-3w72-p2pg Record: https://patchnext.com/advisories/cve-2026-35459 (revision 3, source checked 26 Oct 2026, 13:40 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI pyload-ng: affected <= 0.5.0b3.dev96 ## Suggested inspection (read-only) - `python -m pip show pyload-ng`: prints the installed version. Run with the environment that serves production active. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on pyload-ng. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-7gvf-3w72-p2pg (OSV record GHSA-7gvf-3w72-p2pg lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev96) - Verified: https://github.com/advisories/GHSA-7gvf-3w72-p2pg (GitHub-reviewed advisory GHSA-7gvf-3w72-p2pg lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev96) Commands are suggestions: review each one before running it.
Loading voting…