Security readout for executives and security teams
Plain-English summary
CommonMarker before 0.23.4 can corrupt heap memory when parsing specially shaped Markdown tables. For an application that accepts untrusted Markdown, this could crash the service, leak information, or possibly allow remote code execution without authentication.
Executive priority
Treat as urgent where untrusted Markdown is accepted. Prioritize internet-facing systems first, then internal content workflows that process external submissions or synchronized documents.
Technical view
The issue is a CWE-190 integer overflow in CommonMarker table parsing involving marker rows with more than UINT16_MAX columns. The CVSS 3.1 score is 9.8, network exploitable, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is most likely in web apps, APIs, jobs, or content systems that process attacker-controlled Markdown through commonmarker versions before 0.23.4.
Exploitation context
The provided bundle does not show CISA KEV status or cite active exploitation. Risk remains high because the described condition is unauthenticated, remote, low-complexity, and memory-corruption based.
Researcher notes
The supplied evidence supports the vulnerability class, affected version range, severity, and patch reference. It does not provide proof-of-exploit, observed exploitation, or complete downstream product impact.
Mitigation direction
- Upgrade commonmarker to version 0.23.4 or later.
- Confirm the fixed version is present in production dependency lockfiles.
- Limit untrusted Markdown processing until patched.
- Review vendor advisories for downstream package-specific guidance.
- Regression test Markdown table rendering after upgrading.
Validation and detection
- Inventory applications using the commonmarker package.
- Check dependency manifests and lockfiles for versions below 0.23.4.
- Identify routes or jobs that parse user-supplied Markdown.
- Confirm deployed artifacts use the patched dependency version.
- Review crash telemetry around Markdown parsing paths.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-22051 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/github/cmark-gfm/security/advisories/GHSA-mc3g-88wq-6f4xCVE reference, VulnCheck · vendor-advisory
- https://github.com/gjtorikian/commonmarker/security/advisories/GHSA-fmx4-26r3-wxpfCVE reference, VulnCheck · vendor-advisory
- https://github.com/gjtorikian/commonmarker/commit/ab4504fd17460627a6ab255bc3c63e8e5fc6aed3CVE reference, VulnCheck · patch
- https://github.com/advisories/GHSA-fmx4-26r3-wxpfCVE reference, VulnCheck · vendor-advisory
- https://vulncheck.com/advisories/vc-advisory-GHSA-fmx4-26r3-wxpfCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.