Approved changes feed: RSS · Atom

cpe:2.3:a:cern:indico:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorCern (986b8f22-3802-5da4-976e-546d8dd51a36)
ProductIndico (46ef7625-6a83-54b9-8232-5ba4a0164256)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/indico/indico purl2cpe 2026-06-01 10:12:36.807823
pkg:pypi/indico purl2cpe 2026-06-01 10:12:36.807825

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-33046 vulnerable 2026-06-08 07:57:18.515537 Indico discloses local files resulting in Remote Code Execution through LaTeX injection
Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. In versions prior to 3.3.12, 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. Note that if server-side LaTeX rendering is not in use (ie `XELATEX_PATH` was not set in `indico.conf`), this vulnerability does not apply. It is recommended to update to Indico 3.3.12 as soon as possible. It is also strongly recommended to enable the containerized LaTeX renderer (using `podman`), which isolates it from the rest of the system. As a workaround, 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.
Published: 2026-03-23T22:45:29.067Z
Updated: 2026-03-24T13:42:19.688Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-28352 vulnerable 2026-06-08 07:55:15.174843 Indico missing access check in event series management API
MEDIUM (6.5)
Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. In versions prior to 3.3.11, 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, and modifying an existing event series. 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. Version 3.3.11 fixes the issue. As a workaround, use the webserver to restrict access to the series management API endpoint.
Published: 2026-02-27T21:01:45.740Z
Updated: 2026-03-03T20:29:18.718Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-25739 vulnerable 2026-06-08 07:53:20.278572 Indico affected by Cross-Site-Scripting via material uploads
MEDIUM (5.4)
Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. Versions prior to 3.3.10 are vulnerable to cross-site scripting when uploading certain file types as materials. Users should upgrade to version 3.3.10 to receive a patch. To apply the fix itself updating is sufficient, but to benefit from the strict Content Security Policy (CSP) Indico now applies by default for file downloads, update the webserver config in case one uses nginx with Indico's `STATIC_FILE_METHOD` set to `xaccelredirect`. For further directions, consult the GitHub Security advisory or Indico setup documentation. Some workarounds are available. Use the webserver config to apply a strict CSP for material download endpoints, and/or only let trustworthy users create content (including material uploads, which speakers can typically do as well) on Indico.
Published: 2026-02-19T15:39:32.554Z
Updated: 2026-02-19T19:49:22.187Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-25738 vulnerable 2026-06-08 07:53:20.278089 Indico has Server-Side Request Forgery (SSRF) in multiple places
Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. Versions prior to 3.3.10 are vulnerable to server-side request forgery. Indico makes outgoing requests to user-provides URLs in various places. This is mostly intentional and part of Indico's functionality but is never intended to let users access "special" targets such as localhost or cloud metadata endpoints. Users should upgrade to version 3.3.10 to receive a patch. Those who do not have IPs that expose sensitive data without authentication (typically because they do not host Indico on AWS) are not affected. Only event organizers can access endpoints where SSRF could be used to actually see the data returned by such a request. For those who trust their event organizers, the risk is also very limited. For additional security, both before and after patching, one may also use the common proxy-related environment variables (in particular `http_proxy` and `https_proxy`) to force outgoing requests to go through a proxy that limits requests in whatever way you deem useful/necessary. These environment variables would need to be set both on the indico-uwsgi and indico-celery services.
Published: 2026-02-19T15:30:54.824Z
Updated: 2026-02-19T17:34:39.413Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-59035 vulnerable 2026-06-08 07:35:19.923201 Indico vulnerable to Cross-Site Scripting via LaTeX math code
MEDIUM (4.6)
Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. Prior to version 3.3.8, there is a Cross-Site-Scripting vulnerability when rendering LaTeX math code in contribution or abstract descriptions. Users should to update to Indico 3.3.8 as soon as possible. As a workaround, only let trustworthy users create content on Indico. Note that a conference doing a Call for Abstracts actively invites external speakers (who the organizers may not know and thus cannot fully trust) to submit content, hence the need to update to a a fixed version ASAP in particular when using such workflows.
Published: 2025-09-10T16:03:36.573Z
Updated: 2025-09-11T14:42:48.282Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-59034 vulnerable 2026-06-08 07:35:19.922615 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-53640 vulnerable 2026-06-08 07:31:14.841686 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-50633 vulnerable 2026-06-08 06:52:11.343088 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-45399 vulnerable 2026-06-08 06:48:06.065846 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-37901 vulnerable 2026-06-08 06:08:16.114389 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-30185 vulnerable 2026-06-08 05:31:47.120659 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.