CVE-2026-53530
RaTeX parser aborts on multibyte delimiter, causing process-wide DoS.
Is CVE-2026-53530 being exploited?
Not confirmed. CVE-2026-53530 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-53530?
CVE-2026-53530 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-53530?
Yes. A fix has been recorded for CVE-2026-53530. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53530 affect?
CVE-2026-53530 affects RaTeX < 0.1.11, Applications using ratex_parser::parse(), Web services rendering untrusted LaTeX. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53530?
Upgrade RaTeX to >=0.1.11 and sanitize/validate LaTeX inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote denial-of-service: crafted LaTeX (e.g., \verbéxé) causes parser panic and aborts the entire process, taking rendering services offline.
Patch when possible
- affected< 0.1.11
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.