pyLoad open redirect vulnerability due to improper validation of the is_safe_url function
CVE-2024-24808GHSA-g3cm-qg2v-2hj5
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (pyload-ng 0.5.0b3.dev79), 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.dev79
- Fixed in
- 0.5.0b3.dev79
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-g3cm-qg2v-2hj5 lists affected ranges: PyPI pyload-ng >=0 <0.5.0b3.dev79 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-g3cm-qg2v-2hj5 lists affected ranges: PyPI pyload-ng >=0 <0.5.0b3.dev79
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
- 6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- EPSS
- CVE-2024-24808: 0.55% estimated exploitation activity in the next 30 days; percentile 45.80 (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 Open redirect vulnerability due to incorrect validation of input values when redirecting users after login. Details pyload is validating URLs via the getredirecturl function when redirecting users at login. The URL entered in the next variable goes through the issafeurl function, where a lack of validation can redirect the user to an arbitrary domain. The documentation in the urllib library shows that improper URLs are recognized as relative paths when using the urlparse function. (https://docs.python.org/3/library/urllib.parse.html#urllib.parse.urlparse) For example, When an unusual URL like https:///example.com is entered, urlparse interprets it as a relative path, but in the actual request it is converted to https://example.com due to url normalization. PoC 1. In the next variable, insert the URL to which you want to redirect the user. 2. Check that it is possible to bypass url validation and redirect users to an arbitrary url. Impact An attacker can use this vulnerability…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-g3cm-qg2v-2hj5
- Revision 1 · created ·
Published from osv record GHSA-g3cm-qg2v-2hj5
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-2024-24808 Advisory: pyLoad open redirect vulnerability due to improper validation of the is_safe_url function IDs: CVE-2024-24808, GHSA-g3cm-qg2v-2hj5 Record: https://patchnext.com/advisories/cve-2024-24808 (revision 2, source checked 26 Oct 2026, 13:12 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.1) 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.dev79. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI pyload-ng: affected < 0.5.0b3.dev79; fixed in 0.5.0b3.dev79 ## 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-g3cm-qg2v-2hj5 (OSV record GHSA-g3cm-qg2v-2hj5 lists affected ranges: PyPI pyload-ng >=0 <0.5.0b3.dev79 (fixed)) - Verified: https://github.com/advisories/GHSA-g3cm-qg2v-2hj5 (GitHub-reviewed advisory GHSA-g3cm-qg2v-2hj5 lists affected ranges: PyPI pyload-ng >=0 <0.5.0b3.dev79) Commands are suggestions: review each one before running it.
Loading voting…