Quick answers
- Is CVE-2026-85618 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85618 being exploited in the wild.
- How severe is CVE-2026-85618?
- Medium severity, with a CVSS score of 6.5, published 4 September 2026.
- Which products and versions are affected?
- C4illin ConvertX 0.17.0.
- Is there a fix for CVE-2026-85618?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-85618 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-85618?
- Check whether you run C4illin ConvertX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an arbitrary file read in the xelatex converter component caused by insufficient input sanitization of LaTeX directives. When a user uploads a .tex file, the converter passes it directly to the latexmk/xelatex command without filtering dangerous TeX macros like \input{} and \verbatiminput{} that can reference arbitrary filesystem paths. An authenticated attacker can exploit this by uploading a malicious .tex file containing these directives; the TeX engine then reads the specified files and includes their content in the output PDF. The attack requires authentication and file upload capability. A fix is available in version 0.18.0 or later.
Affected products
- C4illin ConvertX 0.17.0
Timeline
- 2026-09-04: disclosed