Evidence used
- No CISA KEV confirmation is currently recorded.
- A structured source references public exploit or proof-of-concept material.
- EPSS is 0.96% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2023
CVE-2023-22484High confidence
Inefficient Quadratic complexity bug in handle_pointy_brace may lead to a denial of service
github · cmark-gfm
Official source article: GitHub GHSA-24F7-9FRR-5H2R ↗. Check the applicable product and release in the original source.
3.5LowCVSS 3.1
Within 7 days
Fix not verifiedLow technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityLow→Operational priority:Low, unchanged from published severity.unchanged
Compensating controls
- Restrict local access and enforce least privilege on affected hosts.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs github cmark-gfm and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
17 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | cmark-gfm | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.29.0.gfm.13-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian trixietrixie · source | python-cmarkgfm | Vendor fix publishedDebian records a fixed source-package version for this release. | 2024.11.20-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian trixietrixie · source | r-cran-commonmark | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.9.0-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian trixietrixie · source | ruby-commonmarker | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.23.10-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | cmark-gfm | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | python-cmarkgfm | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | r-cran-commonmark | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | ruby-commonmarker | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | cmark-gfm | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.29.0.gfm.13-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | python-cmarkgfm | Vendor fix publishedDebian records a fixed source-package version for this release. | 2024.11.20-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | r-cran-commonmark | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.9.0-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | ruby-commonmarker | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.23.10-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | cmark-gfm | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.29.0.gfm.13-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | python-cmarkgfm | Vendor fix publishedDebian records a fixed source-package version for this release. | 2024.11.20-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | r-cran-commonmark | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.9.0-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | ruby-commonmarker | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.23.10-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · esm-apps | cmark-gfm | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 0.29.0.gfm.6-6ubuntu0.24.04.1~esm1 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Low technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Fix not verified01
What, why and how
cmark-gfm is GitHub's fork of cmark, a CommonMark parsing and rendering library and program in C. Versions prior to 0.29.0.gfm.7 are subject to a polynomial time complexity issue in cmark-gfm that may lead to unbounded resource exhaustion and subsequent denial of service. This vulnerability has been patched in 0.29.0.gfm.7.
What
cmark-gfm is GitHub's fork of cmark, a CommonMark parsing and rendering library and program in C. Versions prior to 0.29.0.gfm.7 are subject to a polynomial time complexity issue in cmark-gfm that may lead to unbounded resource exhaustion and subsequent denial of service. This vulnerability has been patched in 0.29.0.gfm.7.
Why
The product does not properly control the allocation and maintenance of a limited resource.
How
An attacker operating through an adjacent network may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.
What
cmark-gfm is GitHub's fork of cmark, a CommonMark parsing and rendering library and program in C. Versions prior to 0.29.0.gfm.7 are subject to a polynomial time complexity issue in cmark-gfm that may lead to unbounded resource exhaustion and subsequent denial of service. This vulnerability has been patched in 0.29.0.gfm.7.
Why
The product does not properly control the allocation and maintenance of a limited resource.
How
An attacker operating through an adjacent network may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material Reference recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
- Likely attack path
- an adjacent network → Uncontrolled Resource Consumption → disrupt the affected service
- Attack surface
- Adjacent
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-400 ↗
CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.ALowAvailability impact: A successful attack can cause a limited loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix not verified
- Affected
- cmark-gfm: < 0.29.0.gfm.7
- Fixed
- No fixed version is explicitly recorded in the structured CVE data.
- Action
- No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 23 Jan 2023 · Last source change 10 Mar 2025, 21:20 UTC · CWE-400 · Uncontrolled Resource Consumption
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2023-26631
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.