Process abort via unbounded parser recursion
Published Aug 21, 2026 · Updated Aug 25, 2026
Uncontrolled recursion in erweixin RaTeX before 0.1.11 allows remote attackers to crash a rendering process via nested LaTeX. The ratex-parser call chain recursively parses groups and related constructs without a maximum depth, consuming native stack frames until Rust raises a fatal stack-overflow abort. Exposure requires an application to pass untrusted LaTeX into the parser; one small input then terminates the entire hosting process rather than only rejecting the formula.
Summary
What happened
Uncontrolled recursion in erweixin RaTeX before 0.1.11 allows remote attackers to crash a rendering process via nested LaTeX. The ratex-parser call chain recursively parses groups and related constructs without a maximum depth, consuming native stack frames until Rust raises a fatal stack-overflow abort. Exposure requires an application to pass untrusted LaTeX into the parser; one small input then terminates the entire hosting process rather than only rejecting the formula.
The record
- CVE
- CVE-2026-53531
- Published
- Aug 21, 2026
- Updated
- Aug 25, 2026
- Vendor
- erweixin
- Product
- RaTeX
- Classifications
- CWE-674, CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.1.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Nested-LaTeX stack-overflow proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo