CVE-2026-53530

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 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
8.7EG
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: 8.7Exploit: 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, 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.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
70
EG Risk 70/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)
Severity87% × 45%
The EG Score, 8.7 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)

Panic 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-gvrj

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
ratex-parser—
  • every version up to 0.1.11: fixed in 0.1.11
—

Weakness Classification(3)

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

Related CVEs(same product + same CWE)

Same product

1 shown

crates.io:ratex-parser

Frequently asked(5)

What is CVE-2026-53530?
CVE-2026-53530 is a high-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, 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…
When was the CVE record for CVE-2026-53530 published?
The CVE record for CVE-2026-53530 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-53530 actively exploited?
CVE-2026-53530 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-53530?
CVE-2026-53530 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53530?
A fix for CVE-2026-53530 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53530 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-53530

Explore →

Is Your Infrastructure Affected by CVE-2026-53530?

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

Book a Demo →Browse All CVEs