Bug 2512417 - CVE-2026-61632 python-pymdown-extensions: PyMdown Extensions: Information disclosure via path traversal in b64 extension [epel-all]
Summary: CVE-2026-61632 python-pymdown-extensions: PyMdown Extensions: Information dis...
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-pymdown-extensions
Version: epel10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Davide Cavalca
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["6e09fc24-7cb4-4906-9bf6-a...
Depends On:
Blocks: CVE-2026-61632
TreeView+ depends on / blocked
 
Reported: 2026-08-07 07:59 UTC by Marian Rehak
Modified: 2026-08-07 07:59 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Marian Rehak 2026-08-07 07:59:07 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

PyMdown Extensions is a set of extensions for the Python-Markdown markdown project. In versions up to and including 10.21.3, the b64 extension is vulnerable to a path traversal that discloses arbitrary files: it inlines images referenced by <img src="..."> by joining the src onto the configured base_path with os.path.normpath and opening the result directly, without verifying that the resolved path stays inside base_path. As a result, an src containing ../ sequences or an absolute path reads a file outside base_path as long as it has an allowed image extension (.png, .jpg, .jpeg, .gif, .svg), and the file's contents are then base64-encoded into the rendered output, disclosing them. An application that renders untrusted Markdown with pymdownx.b64 enabled can therefore leak the contents of image-extension files readable by the process to whoever controls the Markdown or views the output, a targeted file-read bounded by the extension check. This issue has been fixed in version 11.0.


Note You need to log in before you can comment on or make changes to this bug.