PYSEC-2026-2184

Vulnerability from pysec - Published: 2026-03-23 23:17 - Updated: 2026-07-13 05:49
VLAI
Details

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.

Impacted products
Name purl
indico pkg:pypi/indico

{
  "affected": [
    {
      "ecosystem_specific": {},
      "package": {
        "ecosystem": "PyPI",
        "name": "indico",
        "purl": "pkg:pypi/indico"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.3.12"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.98-rc1",
        "0.98.0",
        "0.98.1",
        "0.98.2",
        "0.99",
        "1.0",
        "1.1",
        "1.1.1",
        "1.1.2",
        "1.2",
        "1.2.1",
        "1.2.1rc10",
        "1.2.1rc11",
        "1.2.1rc2",
        "1.2.1rc4",
        "1.2.1rc5",
        "1.2.1rc6",
        "1.2.1rc7",
        "1.2.1rc9",
        "1.2.2",
        "1.2.2rc1",
        "1.9.11.dev10",
        "1.9.11.dev11",
        "1.9.11.dev12",
        "1.9.11.dev13",
        "1.9.11.dev14",
        "1.9.11.dev15",
        "1.9.11.dev16",
        "1.9.11.dev17",
        "1.9.11.dev3",
        "1.9.11.dev4",
        "1.9.11.dev6",
        "1.9.11.dev7",
        "1.9.11.dev8",
        "1.9.11.dev9",
        "2.0",
        "2.0.1",
        "2.0.2",
        "2.0.3",
        "2.0a1",
        "2.0rc1",
        "2.0rc2",
        "2.1",
        "2.1.1",
        "2.1.10",
        "2.1.11",
        "2.1.2",
        "2.1.3",
        "2.1.4",
        "2.1.5",
        "2.1.6",
        "2.1.7",
        "2.1.8",
        "2.1.9",
        "2.2",
        "2.2.1",
        "2.2.2",
        "2.2.3",
        "2.2.4",
        "2.2.5",
        "2.2.6",
        "2.2.7",
        "2.2.8",
        "2.3",
        "2.3.1",
        "2.3.2",
        "2.3.3",
        "2.3.4",
        "2.3.5",
        "3.0",
        "3.0.1",
        "3.0.2",
        "3.0.3",
        "3.0rc1",
        "3.0rc2",
        "3.1",
        "3.1.1",
        "3.2",
        "3.2.1",
        "3.2.2",
        "3.2.3",
        "3.2.4",
        "3.2.5",
        "3.2.6",
        "3.2.7",
        "3.2.8",
        "3.2.9",
        "3.3",
        "3.3.1",
        "3.3.10",
        "3.3.11",
        "3.3.2",
        "3.3.3",
        "3.3.4",
        "3.3.5",
        "3.3.6",
        "3.3.7",
        "3.3.8",
        "3.3.9"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-33046",
    "GHSA-rm2q-f7jv-3cfp"
  ],
  "details": "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\u0027s 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.",
  "id": "PYSEC-2026-2184",
  "modified": "2026-07-13T05:49:11.074268Z",
  "published": "2026-03-23T23:17:12.520Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/indico/indico/releases/tag/v3.3.12"
    },
    {
      "type": "FIX",
      "url": "https://github.com/indico/indico/commit/0adb70f0ed66e129361d447868f5f3eb90dc5e96"
    },
    {
      "type": "FIX",
      "url": "https://github.com/indico/indico/commit/1dbb12525b3de14229bf4d1ae192988068f975f6"
    },
    {
      "type": "FIX",
      "url": "https://github.com/indico/indico/commit/5f24d23ce9c4b0e4b68b3d0b58987a948fc57c8a"
    },
    {
      "type": "FIX",
      "url": "https://github.com/indico/indico/commit/fb169ced710c30cf792ce4b9f48688db0633cfd8"
    },
    {
      "type": "FIX",
      "url": "https://github.com/indico/indico/security/advisories/GHSA-rm2q-f7jv-3cfp"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…