CVE-2026-25048: xgrammar: Multi-layer nesting causes DoS
xgrammar is an open-source library for efficient, flexible, and portable structured generation. Prior to version 0.1.32, the multi-level nested syntax caused a segmentation fault (core dumped). This issue has been patched in version 0.1.32.
Security readout for executives and security teams
Plain-English summary
CVE-2026-25048 is a denial-of-service flaw in mlc-ai xgrammar before 0.1.32. Specially nested syntax can crash the library with a segmentation fault, interrupting applications that rely on it for structured generation. The published evidence names availability impact, not data theft or privilege gain.
Executive priority
Prioritize remediation for production services using xgrammar, especially externally reachable AI or structured-generation workflows. The main business risk is service disruption, not confirmed data compromise. Patch promptly, but avoid emergency breach assumptions without additional evidence.
Technical view
The issue is classified as CWE-674 and affects xgrammar versions before 0.1.32. Multi-level nested syntax can trigger a segmentation fault and core dump. CVSS 4.0 is 8.7 with network, low-complexity, no-auth, no-user-interaction characteristics and high vulnerable-system availability impact.
Likely exposure
Exposure is likely where applications or services use mlc-ai xgrammar below 0.1.32, especially if they process user-controlled grammar or structured-generation syntax. Red Hat advisories are listed, so packaged deployments should verify vendor applicability rather than assuming upstream-only exposure.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. The advisory describes a crash condition rather than exploit code. Treat internet-facing or multi-tenant parsing paths as higher urgency because unauthenticated input may affect service availability.
Researcher notes
Sources identify the trigger class as multi-layer nesting and the failure mode as segmentation fault. Public details in the bundle do not establish precise parser internals, exploit circulation, or downstream product impact beyond listed xgrammar and Red Hat tracking references.
Mitigation direction
Upgrade mlc-ai xgrammar to version 0.1.32 or later.
Apply relevant Red Hat errata where xgrammar is vendor-packaged.
Limit untrusted nested syntax input until fixed.
Review vendor guidance for environment-specific remediation details.
Monitor affected services for crashes or core dumps.
Validation and detection
Inventory SBOMs, lockfiles, images, and runtimes for xgrammar.
Confirm deployed xgrammar versions are 0.1.32 or later.
Check logs for segmentation faults or unexplained parser crashes.
Verify Red Hat advisory applicability for managed packages.
Run non-destructive resilience tests against structured-generation parsing paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-674: 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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-674 · source CWE mapping
Uncontrolled Recursion
Uncontrolled Recursion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.