pyLoad: Improper Neutralization of Special Elements used in an OS Command
CVE-2026-35463GHSA-w48f-wwwf-f5fr
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-w48f-wwwf-f5fr 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-w48f-wwwf-f5fr 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
- 8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-35463: 0.81% estimated exploitation activity in the next 30 days; percentile 57.12 (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 ADMINONLYOPTIONS protection mechanism restricts security-critical configuration values (reconnect scripts, SSL certs, proxy credentials) to admin-only access. However, this protection is only applied to core config options, not to plugin config options. The AntiVirus plugin stores an executable path (avfile) in its config, which is passed directly to subprocess.Popen(). A non-admin user with SETTINGS permission can change this path to achieve remote code execution. Details Safe wrapper — ADMINONLYOPTIONS (core/api/init.py:225-235): Where it IS enforced — core config (core/api/init.py:255): Where it is NOT enforced — plugin config (core/api/init.py:271-272): Dangerous sink — AntiVirus plugin (plugins/addons/AntiVirus.py:75): PoC Additional Finding: Arbitrary File Read via storagefolder The storagefolder validation at core/api/init.py:238-246 uses inverted logic — it prevents the new value from being INSIDE protected directories, but not from being an ANCESTOR of…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-w48f-wwwf-f5fr
- Revision 1 · created ·
Published from osv record GHSA-w48f-wwwf-f5fr
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-35463 Advisory: pyLoad: Improper Neutralization of Special Elements used in an OS Command IDs: CVE-2026-35463, GHSA-w48f-wwwf-f5fr Record: https://patchnext.com/advisories/cve-2026-35463 (revision 2, 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: High (CVSS 8.8) 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-w48f-wwwf-f5fr (OSV record GHSA-w48f-wwwf-f5fr lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev96) - Verified: https://github.com/advisories/GHSA-w48f-wwwf-f5fr (GitHub-reviewed advisory GHSA-w48f-wwwf-f5fr lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev96) Commands are suggestions: review each one before running it.
Loading voting…