# CVE-2026-75597: pyLoad: Unauthenticated access to /web/ bypasses authentication on sensitive templates and leaks internal error details via exception attribute typo > Unauthenticated attackers can access sensitive web templates and leak internal error details in pyLoad due to missing authentication checks on a specific route. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Oct 2026 - **Updated:** 9 Oct 2026 - **Also known as:** GHSA-j92p-c242-7hfx, PYSEC-2026-4292 ## What is CVE-2026-75597? CVE-2026-75597 is a medium-severity missing authorization vulnerability in pyload, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev101, the `/web/` route in `src/pyload/webui/app/blueprints/app_blueprint.py` renders Jinja2 templates without any authentication requirement. Every equivalent direct route (`/logs`, `/settings`, `/queue`, `/dashboard`, etc.) is protected by `@login_required`, but the underlying templates for all of these pages are accessible unauthenticated via this endpoint. Combined with an exception attribute typo in `src/pyload/webui/app/handlers.py` (`exc.desc` instead of `exc.description`), internal Jinja2 variable names are leaked in HTTP 500 response bodies to unauthenticated callers. An attacker can also enumerate all valid template names by observing 200 vs 500 response differentiation. Version 0.5.0b3.dev101 contains a patch. Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-209 (Generation of Error Message Containing Sensitive Information) ## Which versions are affected by CVE-2026-75597? 3 open source packages ship an affected version, including pyload-ng. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pyload-ng` | PyPI | All versions | 0.5.0b3.dev101 | | `pyload-ng` | PyPI | All versions | 0.5.0b3.dev101 | | `pyload-ng` | PyPI | All versions | 0.5.0b3.dev101 | ## How do I fix CVE-2026-75597? Upgrade pyload-ng to 0.5.0b3.dev101 or later. ## Is CVE-2026-75597 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75597 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-75597 and fix it if it is affected. What it is: CVE-2026-75597 is a medium-severity missing authorization vulnerability in pyload, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75597 exists. Affected packages and fixed versions: - pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev101 - pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev101 - pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev101 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-75597/ (Markdown: https://insights.sbomify.com/CVE-2026-75597/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75597 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75597 - OSV: https://osv.dev/vulnerability/CVE-2026-75597 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-75597/ Summaries are generated and may contain mistakes; the official description above is the record.