GHSA-hgmg-hhc8-g5wr
MEDIUMGHSA-hgmg-hhc8-g5wr is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in @ckeditor/ckeditor5-markdown-gfm. O3 Security confirms whether GHSA-hgmg-hhc8-g5wr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
CKEditor 5 Markdown plugin Regular expression Denial of Service
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@ckeditor/ckeditor5-markdown-gfmnpmDescription
Impact
A regular expression denial of service (ReDoS) vulnerability has been discovered in the CKEditor 5 Markdown plugin code. The vulnerability allowed to abuse a link recognition regular expression, which could cause a significant performance drop resulting in a browser tab freeze. It affects all users using the CKEditor 5 Markdown plugin at version <= 24.0.0.
Patches
The problem has been recognized and patched. The fix will be available in version 25.0.0.
Workarounds
The user can work around the issue by:
- Upgrading CKEditor 5 to version 25.0.0.
- Disabling the Markdown plugin.
More information
If you have any questions or comments about this advisory:
- Email us at [email protected]
Acknowledgements
The CKEditor 5 team would like to thank Erik Krogh Kristensen from the GitHub team for recognizing this vulnerability and Alvaro Muñoz from GitHub for reporting it.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @ckeditor/ckeditor5-markdown-gfm | all versions | 25.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @ckeditor/ckeditor5-markdown-gfm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @ckeditor/ckeditor5-markdown-gfm to 25.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hgmg-hhc8-g5wr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hgmg-hhc8-g5wr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-hgmg-hhc8-g5wr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-hgmg-hhc8-g5wr in your dependencies?
O3 detects GHSA-hgmg-hhc8-g5wr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.