Vulnerability in ratex-parser (CVE-2026-53530)
Summary
Vulnerability in ratex-parser (CVE-2026-53530). Risk of unauthorized operations or information disclosure. Exploitable via parse_symbol_inner. Mitigation: upgrade to 0.1.11 or later.
Original description
The description as published by the source.
Summary
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.
Details
Affected code
crates/ratex-parser/src/parser.rs, parse_symbol_inner:
if let Some(stripped) = text.strip_prefix("\\verb") { // parser.rs:901
self.consume();
let arg = stripped.to_string(); // e.g. "éxé"
let star = arg.starts_with('*');
let arg = if star { &arg[1..] } else { &arg }; // parser.rs:905 (also byte-sliced)
if arg.len() < 2 { // byte length
return Err(ParseError::new("\\verb assertion failed", Some(&nucleus)));
}
let body = arg[1..arg.len() - 1].to_string(); // parser.rs:910 <-- PANIC on multibyte delimiter
...
}
For input \verbéxé: arg = "éxé", where é = U+00E9 (bytes C3 A9). arg.len() is the byte length (5), the < 2 guard pas…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53530 has been found in ratex-parser.
Attackers can target a specific entry point like parse_symbol_inner over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ratex-parser to 0.1.11 or later.
If unsure, ask your IT team or search "ratex-parser CVE-2026-53530" on the vendor's site.
CVE-2026-53530 (ratex-parser) — CWE-248
Attack surface: parse_symbol_inner / lexer.rs / lex_verb / catch_unwind
Patched: 0.1.11 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-248) exists in ratex-parser. Attackers reach the vulnerable code path via parse_symbol_inner.
Check the vendor advisory for the affected versions of ratex-parser. Attack surface: parse_symbol_inner / lexer.rs / lex_verb / catch_unwind.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.1.11.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ratex-parser' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ratex-parser' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ratex-parserを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ratex-parser to 0.1.11ステージング環境で 0.1.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com