mangadex-downloader vulnerable to unauthorized file reading
CVE-2022-36082GHSA-r9x7-2xmr-v8fw
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (mangadex-downloader 1.7.2), 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 mangadex-downloader
- Affected
- >= 1.3.0, < 1.7.2
- Fixed in
- 1.7.2
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-r9x7-2xmr-v8fw lists affected ranges: PyPI mangadex-downloader >=1.3.0 <1.7.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-r9x7-2xmr-v8fw lists affected ranges: PyPI mangadex-downloader >=1.3.0 <1.7.2
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
- 6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2022-36082: 0.72% estimated exploitation activity in the next 30 days; percentile 53.85 (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.
Impact When using file:<location command and <location is web URL location (http, https). mangadex-downloader will try to open and read a file in local disk if the content from online file is exist-as-a-file in victim computer So far, the app only read the files and not execute it. But still, when someone reading your files without you knowing, it's very scary. Proof of Concept (PoC) https://www.mansuf.link/unauthorized-file-read-in-mangadex-downloader-cve-2022-36082/ Workarounds Unfortunately, there is no workarounds to make it safe from this issue. But i suggest you double check the url before proceed to download or update to latest version ( = 1.7.2) Patches Fixed in version 1.7.2. Commit patch: https://github.com/mansuf/mangadex-downloader/commit/439cc2825198ebc12b3310c95c39a8c7710c9b42
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-r9x7-2xmr-v8fw
- 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-r9x7-2xmr-v8fw
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-2022-36082 Advisory: mangadex-downloader vulnerable to unauthorized file reading IDs: CVE-2022-36082, GHSA-r9x7-2xmr-v8fw Record: https://patchnext.com/advisories/cve-2022-36082 (revision 3, source checked 26 Oct 2026, 13:21 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: mangadex-downloader 1.7.2. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI mangadex-downloader: affected >= 1.3.0, < 1.7.2; fixed in 1.7.2 ## Suggested inspection (read-only) - `python -m pip show mangadex-downloader`: 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 mangadex-downloader. - 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-r9x7-2xmr-v8fw (OSV record GHSA-r9x7-2xmr-v8fw lists affected ranges: PyPI mangadex-downloader >=1.3.0 <1.7.2 (fixed)) - Verified: https://github.com/advisories/GHSA-r9x7-2xmr-v8fw (GitHub-reviewed advisory GHSA-r9x7-2xmr-v8fw lists affected ranges: PyPI mangadex-downloader >=1.3.0 <1.7.2) Commands are suggestions: review each one before running it.
Loading voting…