Staging Environment: Content and features may be unstable or change without notice.
Search for packages
Package details: pkg:pypi/indico@3.3.11
purl pkg:pypi/indico@3.3.11
Next non-vulnerable version 3.3.12
Latest non-vulnerable version 3.3.12
Risk 4.0
Vulnerabilities affecting this package (1)
Vulnerability Summary Fixed by
VCID-px34-3ut4-cyeu
Aliases:
CVE-2026-33046
GHSA-rm2q-f7jv-3cfp
Indico discloses local files resulting in Remote Code Execution through LaTeX injection > [!NOTE] > If server-side LaTeX rendering is not in use (ie `XELATEX_PATH` was not set in `indico.conf`), this vulnerability does not apply. ### Impact Due to vulnerabilities in TeXLive and obscure LaTeX syntax that allowed circumventing Indico's LaTeX sanitizer, it is possible to use specially-crafted LaTeX snippets which can read local files or execute code with the privileges of the user running Indico on the server. ### Patches It is recommended to update to [Indico 3.3.12](https://github.com/indico/indico/releases/tag/v3.3.12) as soon as possible. See [the docs](https://docs.getindico.io/en/stable/installation/upgrade/) for instructions on how to update. It is also strongly recommended to enable the containerized LaTeX renderer (using `podman`), which isolates it from the rest of the system. See [the docs](https://docs.getindico.io/en/stable/installation/upgrade/#upgrading-to-3-3-12) for details - it is very easy and from now on the only recommended/supported way of using LaTeX. ### Workarounds Remove the `XELATEX_PATH` setting from `indico.conf` (or comment it out or set it to `None`) and restart the `indico-uwsgi` and `indico-celery` services to disable LaTeX functionality. ### For more information For any questions or comments about this advisory: - Open a thread in [the forum](https://talk.getindico.io/) - Send an email to [indico-team@cern.ch](mailto:indico-team@cern.ch)
3.3.12
Affected by 0 other vulnerabilities.
Vulnerabilities fixed by this package (1)
Vulnerability Summary Aliases
VCID-rdjk-wdan-aucm Indico has a missing access check in the event series management API The API endpoint used to manage event series is missing an access check, allowing unauthenticated/unauthorized access to this endpoint. The impact of this is limited to: - Getting the metadata (title, category chain, start/end date) for events in an existing series - Deleting an existing event series: This just removes the series metadata, ie (if enabled) the links between events in the same series and the lecture series number in the event title - Modifying an existing event series: Just like for deleting, it would only allow to toggle the metadata display. It could also be used to set an event title pattern for the series, but this is only used when cloning an event from that series. That this vulnerability does NOT allow unauthorized access to events (beyond the basic metadata mentioned above), nor any kind of tampering with user-visible data in events. CVE-2026-28352
GHSA-rfpp-2hgm-gp5v

Date Actor Action Vulnerability Source VulnerableCode Version
2026-06-06T07:33:31.500423+00:00 GitLab Importer Affected by VCID-px34-3ut4-cyeu https://gitlab.com/gitlab-org/advisories-community/-/blob/main/pypi/indico/CVE-2026-33046.yml 38.6.0
2026-06-05T22:02:02.876333+00:00 GHSA Importer Fixing VCID-rdjk-wdan-aucm https://github.com/advisories/GHSA-rfpp-2hgm-gp5v 38.6.0
2026-06-04T16:57:33.386662+00:00 GithubOSV Importer Fixing VCID-rdjk-wdan-aucm https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/03/GHSA-rfpp-2hgm-gp5v/GHSA-rfpp-2hgm-gp5v.json 38.6.0
2026-06-02T04:51:00.488848+00:00 GitLab Importer Fixing VCID-rdjk-wdan-aucm https://gitlab.com/gitlab-org/advisories-community/-/blob/main/pypi/indico/CVE-2026-28352.yml 38.6.0