Server-side Request Forgery (SSRF) via img tags in reportlab
CVE-2020-28463GHSA-mpvw-25mg-59vx
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (reportlab 3.5.55), 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 reportlab
- Affected
- < 3.5.55
- Fixed in
- 3.5.55
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-mpvw-25mg-59vx lists affected ranges: PyPI reportlab >=0 <3.5.55 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-mpvw-25mg-59vx lists affected ranges: PyPI reportlab >=0 <3.5.55
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
- 7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2020-28463: 1.35% estimated exploitation activity in the next 30 days; percentile 71.46 (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.
All versions of package reportlab at time of writing are vulnerable to Server-side Request Forgery (SSRF) via img tags. In order to reduce risk, use trustedSchemes & trustedHosts (see in Reportlab's documentation) Steps to reproduce by Karan Bamal: 1. Download and install the latest package of reportlab 2. Go to demos - odyssey - dodyssey 3. In the text file odyssey.txt that needs to be converted to pdf inject <img src="http://127.0.0.1:5000" valign="top"/ 4. Create a nc listener nc -lp 5000 5. Run python3 dodyssey.py 6. You will get a hit on your nc showing we have successfully proceded to send a server side request 7. dodyssey.py will show error since there is no img file on the url, but we are able to do SSRF
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-mpvw-25mg-59vx
- 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-mpvw-25mg-59vx
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-2020-28463 Advisory: Server-side Request Forgery (SSRF) via img tags in reportlab IDs: CVE-2020-28463, GHSA-mpvw-25mg-59vx Record: https://patchnext.com/advisories/cve-2020-28463 (revision 3, source checked 26 Oct 2026, 13:23 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: reportlab 3.5.55. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI reportlab: affected < 3.5.55; fixed in 3.5.55 ## Suggested inspection (read-only) - `python -m pip show reportlab`: 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 reportlab. - 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-mpvw-25mg-59vx (OSV record GHSA-mpvw-25mg-59vx lists affected ranges: PyPI reportlab >=0 <3.5.55 (fixed)) - Verified: https://github.com/advisories/GHSA-mpvw-25mg-59vx (GitHub-reviewed advisory GHSA-mpvw-25mg-59vx lists affected ranges: PyPI reportlab >=0 <3.5.55) Commands are suggestions: review each one before running it.
Loading voting…