RaTeX is a KaTeX-compatible math rendering engine written in Rust. Prior to version 0.1.11, the public parser entrypoint ratex_parser::parse(&str) panics on the 9-byte input \verbéxé (i.e. \verb followed by the non-ASCII delimiter é). When handling a \verb command, the parser slices the verbatim argument with byte indices (arg[1..arg.len() - 1]); if the delimiter character is multibyte UTF-8, index 1 lands inside that character and Rust panics with *“byte index 1 is not a char boundary”*. Because RaTeX’s release profile sets panic = "abort" (Cargo.toml:48), the panic aborts the entire process — not just the current request/thread — making this a hard denial of service for any service that renders untrusted LaTeX. Version 0.1.11 fixes the issue.
CVE-2026-53530
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 70(Attend)EG Risk 70/100SSVC: Attend
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 computedSeverity87% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
July 7, 2026
Last Modified
August 24, 2026
Advisory Details (1)
Auto-updated Aug 21, 2026Panic on `\verb` with a multibyte delimiter (UTF-8 byte-boundary slice) · Advisory · erweixin/RaTeX · GitHub
https://github.com/erweixin/RaTeX/security/advisories/GHSA-4hgp-59h5-gvrjVendor Advisories for CVE-2026-53530(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ratex-parser | — | 0.1.11 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-08-30 07:40 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 21:54 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 01:51 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 12:57 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 10:17 UTCEG score recompute
- 2026-08-24 20:29 UTCEG score recompute
- 2026-08-24 20:12 UTCEG score recompute
- 2026-08-24 11:11 UTCEG score recompute
- 2026-08-23 10:46 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 22:27 UTCEG score recompute
- 2026-08-21 21:40 UTCEG score recompute▲ 8.70
- 2026-08-21 21:39 UTCMITRE cvelistV5CVSS v3 → 8.7 · CVSS v4 → 8.7
- 2026-08-01 23:58 UTCEG score recompute
- 2026-07-26 12:34 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-08 00:12 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-400
Frequently asked(5)
What is CVE-2026-53530?
When was CVE-2026-53530 disclosed?
Is CVE-2026-53530 actively exploited?
What is the CVSS score of CVE-2026-53530?
How do I remediate CVE-2026-53530?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53530
Is Your Infrastructure Affected by CVE-2026-53530?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.