CVE-2026-124683
CVE-2026-124683 is a high-severity vulnerability with a CVSS 4.0 base score of 8.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-407.
Key facts
- Severity: High (CVSS 4.0 base score 8.7)
- EPSS exploit prediction: 0% (43rd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-407
- Published:
- Last modified:
Description
Eclipse Langium versions 3.2.0 through 4.4.0 contain an inefficient algorithmic complexity issue (CWE-407) in the opt-in IndentationAwareTokenBuilder and IndentationAwareLexer. When producing DEDENT tokens, the token builder recomputes line numbers by re-scanning the entire preceding document text. A document whose indentation changes on most lines then takes quadratic time to tokenize. Because tokenization is synchronous, a crafted document of a few hundred kilobytes can block the Node.js event loop for tens of seconds. That causes a DoS for every user served by the same process. Languages built with the DefaultLexer and DefaultTokenBuilder are unaffected.
Frequently asked questions
- What is CVE-2026-124683?
- Eclipse Langium versions 3.2.0 through 4.4.0 contain an inefficient algorithmic complexity issue (CWE-407) in the opt-in IndentationAwareTokenBuilder and IndentationAwareLexer. When producing DEDENT tokens, the token builder recomputes line numbers by re-scanning the entire preceding document text. A document whose indentation changes on most lines then takes quadratic time to tokenize. Because tokenization is synchronous, a crafted document of a few hundred kilobytes can block the Node.js event loop for tens of seconds. That causes a DoS for every user served by the same process. Languages built with the DefaultLexer and DefaultTokenBuilder are unaffected.
- How severe is CVE-2026-124683?
- CVE-2026-124683 has a CVSS 4.0 base score of 8.7, rated high severity.
- Is CVE-2026-124683 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (43rd percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2026-124683?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2026-124683 published?
- CVE-2026-124683 was published on 2026-11-09 and last updated on 2026-11-12.
References
- https://github.com/eclipse-langium/langium/security/advisories/GHSA-297v-g8mm-qj4h
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/553
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1069
Other CWE-407 vulnerabilities
- CVE-2026-123792 — High (CVSS 8.7): The Symfony Yaml components Inline and Parser, parse some YAML documents inefficiently, so that a small crafted…
- CVE-2026-113436 — High (CVSS 8.7): Inefficient Algorithmic Complexity vulnerability in the header integer parser of mtrudel bandit allows an…
- CVE-2026-108529 — High (CVSS 8.7): Inefficient Algorithmic Complexity vulnerability in the HTTP/2 implementation of mtrudel bandit allows an…
- CVE-2026-16762 — High (CVSS 8.7): An attacker able to supply a crafted XML document to an application using QXmlStreamReader can cause disproportionate…
- CVE-2026-114143 — High (CVSS 8.7): toml-node is a TOML parser for Node.js and the browser. Prior to 5.0.1, toml.parse() repeatedly slices and rejoins…
- CVE-2026-114141 — High (CVSS 8.7): toml-node is a TOML parser for Node.js and the browser. Prior to 5.0.1, the toml.parse() compiler's addTableArray()…