PYSEC-2025-235

Vulnerability from pysec - Published: 2025-04-09 16:15 - Updated: 2026-05-20 09:19
VLAI?
Details

XGrammar is an open-source library for efficient, flexible, and portable structured generation. Prior to 0.1.18, Xgrammar includes a cache for compiled grammars to increase performance with repeated use of the same grammar. This cache is held in memory. Since the cache is unbounded, a system making use of xgrammar can be abused to fill up a host's memory and case a denial of service. For example, sending many small requests to an LLM inference server with unique JSON schemas would eventually cause this denial of service to occur. This vulnerability is fixed in 0.1.18.

Impacted products
Name purl
xgrammar pkg:pypi/xgrammar

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "xgrammar",
        "purl": "pkg:pypi/xgrammar"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.1.18"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.1.0",
        "0.1.1",
        "0.1.10",
        "0.1.11",
        "0.1.12",
        "0.1.13",
        "0.1.14",
        "0.1.15",
        "0.1.16",
        "0.1.17",
        "0.1.2",
        "0.1.3",
        "0.1.4",
        "0.1.4rc2",
        "0.1.5",
        "0.1.5rc1",
        "0.1.6",
        "0.1.7",
        "0.1.8",
        "0.1.9"
      ]
    }
  ],
  "aliases": [
    "CVE-2025-32381",
    "GHSA-389x-67px-mjg3"
  ],
  "details": "XGrammar is an open-source library for efficient, flexible, and portable structured generation. Prior to 0.1.18, Xgrammar includes a cache for compiled grammars to increase performance with repeated use of the same grammar. This cache is held in memory. Since the cache is unbounded, a system making use of xgrammar can be abused to fill up a host\u0027s memory and case a denial of service. For example, sending many small requests to an LLM inference server with unique JSON schemas would eventually cause this denial of service to occur. This vulnerability is fixed in 0.1.18.",
  "id": "PYSEC-2025-235",
  "modified": "2026-05-20T09:19:24.371536Z",
  "published": "2025-04-09T16:15:26.210Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/mlc-ai/xgrammar/security/advisories/GHSA-389x-67px-mjg3"
    },
    {
      "type": "FIX",
      "url": "https://github.com/mlc-ai/xgrammar/pull/243"
    },
    {
      "type": "FIX",
      "url": "https://github.com/vllm-project/vllm/pull/16283"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…