pyload-ng: SSRF via HTTP Redirect Bypass in parse_urls API
CVE-2026-46561GHSA-8rp3-xc6w-5qp5
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (pyload-ng 0.5.0b3.dev100), redeploy, then verify what is actually installed.
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.dev100
- Fixed in
- 0.5.0b3.dev100
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-8rp3-xc6w-5qp5 lists affected ranges: PyPI pyload-ng >=0 <0.5.0b3.dev100 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-8rp3-xc6w-5qp5 lists affected ranges: PyPI pyload-ng >=0 <0.5.0b3.dev100
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
- 5.0 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
- EPSS
- CVE-2026-46561: 0.18% estimated exploitation activity in the next 30 days; percentile 7.08 (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 SSRF mitigation added in commit 33c55da for GHSA-7gvf-3w72-p2pg is incomplete. The PREREQFUNCTION-based private IP check was correctly applied to HTTPChunk (download path) but not to HTTPRequest (used by the parseurls API). An authenticated attacker can supply a URL pointing to an attacker-controlled server that responds with a 302 redirect to an internal/private IP address, bypassing the isglobalhost() check on the initial URL. Details The parseurls API method validates the initial URL hostname: geturl() is imported from requestfactory.py and creates an HTTPRequest with default settings: HTTPRequest.init sets allowprivateip = True by default: The inithandle() method enables redirect following: The prerequestcallback that should block redirects to private IPs is a no-op when allowprivateip is True: The fix at commit 33c55da correctly set allowprivateip = False in HTTPChunk (httpchunk.py:136) for the download path, but HTTPRequest used by RequestFactory.geturl() retains…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-8rp3-xc6w-5qp5
- Revision 1 · created ·
Published from osv record GHSA-8rp3-xc6w-5qp5
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-46561 Advisory: pyload-ng: SSRF via HTTP Redirect Bypass in parse_urls API IDs: CVE-2026-46561, GHSA-8rp3-xc6w-5qp5 Record: https://patchnext.com/advisories/cve-2026-46561 (revision 2, source checked 26 Oct 2026, 13:45 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.0) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: pyload-ng 0.5.0b3.dev100. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI pyload-ng: affected < 0.5.0b3.dev100; fixed in 0.5.0b3.dev100 ## Suggested inspection (read-only) - `python -m pip show pyload-ng`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## 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-8rp3-xc6w-5qp5 (OSV record GHSA-8rp3-xc6w-5qp5 lists affected ranges: PyPI pyload-ng >=0 <0.5.0b3.dev100 (fixed)) - Verified: https://github.com/advisories/GHSA-8rp3-xc6w-5qp5 (GitHub-reviewed advisory GHSA-8rp3-xc6w-5qp5 lists affected ranges: PyPI pyload-ng >=0 <0.5.0b3.dev100) Commands are suggestions: review each one before running it.
Loading voting…