Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.7amended

PyMdown Extensions has a ReDOS bug in its Figure Capture extension

CVE-2025-68142GHSA-r6h4-mm7h-8pmq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (pymdown-extensions 10.16.1), 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.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U · score source
EPSS
  • CVE-2025-68142: 0.48% estimated exploitation activity in the next 30 days; percentile 41.74 (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 This issue describes a ReDOS bug found within the figure caption extension (pymdownx.blocks.caption ). In systems that take unchecked user content, this could cause long hangs when processing the data if a malicious payload was crafted. Patches This issue is patched in Release 10.16.1. Workarounds Some possible workarounds If users are concerned about this vulnerability and process unknown user content without timeouts or other safeguards in place to prevent really large, malicious content being aimed at systems, the use of pymdownx.blocks.caption could be avoided until the library is updated to 10.16.1+. References The original issue https://github.com/facelessuser/pymdown-extensions/issues/2716. Description The original issue came through PyMdown Extensions' normal issue tracker instead of the typical security flow: https://github.com/facelessuser/pymdown-extensions/issues/2716. Because this came through the normal issue flow, it was handled as a normal issue. In the future,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-r6h4-mm7h-8pmq

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-r6h4-mm7h-8pmq

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-2025-68142

Advisory: PyMdown Extensions has a ReDOS bug in its Figure Capture extension
IDs: CVE-2025-68142, GHSA-r6h4-mm7h-8pmq
Record: https://patchnext.com/advisories/cve-2025-68142 (revision 3, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pymdown-extensions 10.16.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pymdown-extensions: affected < 10.16.1; fixed in 10.16.1

## Suggested inspection (read-only)
- `python -m pip show pymdown-extensions`: 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 pymdown-extensions.
- 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-r6h4-mm7h-8pmq (OSV record GHSA-r6h4-mm7h-8pmq lists affected ranges: PyPI pymdown-extensions >=0 <10.16.1 (fixed))
- Verified: https://github.com/advisories/GHSA-r6h4-mm7h-8pmq (GitHub-reviewed advisory GHSA-r6h4-mm7h-8pmq lists affected ranges: PyPI pymdown-extensions >=0 <10.16.1)

Commands are suggestions: review each one before running it.

Loading voting…