Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository lepture/mistune. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Security advisory published by the maintainers of lepture/mistune for mistune: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.
Patch / fix
- pypi mistune 3.2.1
Is GHSA-hjph-f4mc-wx4c in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | mistune | 3.2.0 |
3.2.1 |
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
Sources
- GitHub Advisory GHSA-hjph-f4mc-wx4c
- Maintainer advisory GHSA-hjph-f4mc-wx4c
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of lepture/mistune published their own advisory on GitHub. Reviewed sources take precedence over it.