CVE-2026-53531

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
6.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

RaTeX is a KaTeX-compatible math rendering engine written in Rust. Prior to version 0.1.11, RaTeX’s recursive-descent parser recurses one (or more) native stack frame per nesting level at {, \left, \sqrt{, ^{, etc, with no maximum depth limit. A short, ~10 KB input of nested groups overflows the 8 MB main-thread stack and aborts the process. With panic = "abort" (Cargo.toml:48), and because a Rust stack overflow is always a fatal SIGABRT regardless of panic strategy this is an unrecoverable, whole-process denial of service reachable from a single untrusted LaTeX string. Version 0.1.11 fixes the issue.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
62
EG Risk 62/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity69% × 45%
The EG Score, 6.9 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 7, 2026

Last Modified

October 12, 2026

Advisory Details (1)

Auto-updated Aug 21, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Unbounded parser recursion → stack overflow (process abort) · Advisory · erweixin/RaTeX · GitHub

https://github.com/erweixin/RaTeX/security/advisories/GHSA-4w5h-hx6r-28q7

Vendor Advisories for CVE-2026-53531(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
ratex-parser—
  • every version up to 0.1.11: fixed in 0.1.11
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-12 15:57 UTCEG score recompute
  4. 2026-10-11 19:40 UTCEG score recompute
  5. 2026-10-11 16:55 UTCEG score recompute
  6. 2026-10-11 14:19 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-10-01 16:25 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-09-28 13:34 UTCEG score recompute
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 43 more
  1. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-09-23 06:15 UTCEG score recompute
  3. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-09-18 05:48 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-09-14 11:19 UTCEG score recompute
  9. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-09-13 08:29 UTCEG score recompute
  11. 2026-09-12 03:41 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  14. 2026-09-09 22:57 UTCEG score recompute
  15. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-09-05 22:53 UTCEG score recompute
  19. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  23. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-08-30 07:40 UTCEG score recompute
  25. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  26. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  27. 2026-08-28 04:30 UTCEG score recompute
  28. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  29. 2026-08-27 01:51 UTCEG score recompute
  30. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  31. 2026-08-25 17:26 UTCEG score recompute
  32. 2026-08-25 17:03 UTCEG score recompute
  33. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  34. 2026-08-25 06:21 UTCEG score recompute
  35. 2026-08-23 00:43 UTCEG score recompute
  36. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  37. 2026-08-21 22:27 UTCEG score recompute
  38. 2026-08-21 21:40 UTCEG score recomputeFirst assessed: 6.9 MEDIUM
  39. 2026-08-21 21:39 UTCMITRE cvelistV5CVSS v3 → 6.9 · CVSS v4 → 6.9
  40. 2026-08-02 04:11 UTCEG score recompute
  41. 2026-07-26 12:34 UTCEG score recompute
  42. 2026-07-23 03:19 UTCEG score recompute
  43. 2026-07-08 00:12 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-53531?
CVE-2026-53531 is a medium-severity vulnerability; its CVE record was published on July 7, 2026. RaTeX is a KaTeX-compatible math rendering engine written in Rust. Prior to version 0.1.11, RaTeX’s recursive-descent parser recurses one (or more) native stack frame per nesting level at {, \left, \sqrt{, ^{, etc, with no maximum depth limit. A short, ~10 KB input of nested groups overflows the 8…
When was the CVE record for CVE-2026-53531 published?
The CVE record for CVE-2026-53531 was published on July 7, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-53531 actively exploited?
CVE-2026-53531 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53531?
CVE-2026-53531 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53531?
A fix for CVE-2026-53531 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53531 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53531

Explore →

Is Your Infrastructure Affected by CVE-2026-53531?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.