Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Indico versions before 3.3.12 are vulnerable only where server-side LaTeX rendering is enabled (XELATEX_PATH set in indico.conf). An attacker who can submit specially crafted LaTeX content can bypass the LaTeX sanitizer and read local files or execute code as the user running Indico. Upgrade to Indico 3.3.12; if you cannot upgrade, remove XELATEX_PATH from indico.conf and restart the services to disable LaTeX rendering.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.7 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0081, the 57th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:04 UTC First seen by agentprime
- 31 Oct 2026, 15:04 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-rm2q-f7jv-3cfp
- OSV: GHSA-rm2q-f7jv-3cfp
- github.com/indico/indico/security/advisories/GHSA-rm2q-f7jv-3cfp
- nvd.nist.gov/vuln/detail/CVE-2026-33046
- github.com/indico/indico/commit/0adb70f0ed66e129361d447868f5f3eb90dc5e96
- github.com/indico/indico/commit/1dbb12525b3de14229bf4d1ae192988068f975f6
- github.com/indico/indico/commit/5f24d23ce9c4b0e4b68b3d0b58987a948fc57c8a
- github.com/indico/indico/commit/fb169ced710c30cf792ce4b9f48688db0633cfd8
- github.com/indico/indico
- github.com/indico/indico/releases/tag/v3.3.12