CVE-2026-107394: Indico incomplete SSRF check in URL validation

CVE-2026-107394 · Severity: medium · CVSS 6.8 · Published 2026-10-08

Indico, a conference management system, makes outgoing requests to user-provided URLs. A flaw in the server-side request forgery (SSRF) protection allows attackers to bypass validation and target sensitive endpoints like localhost or cloud metadata services. Event organizers can exploit this to access data from internal systems or cloud infrastructure, potentially exposing credentials and configuration details.

Technologies: Indico, indico (PyPI). Vendors: Indico, PyPI.

Quick answers

Is CVE-2026-107394 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-107394 being exploited in the wild.
How severe is CVE-2026-107394?
Medium severity, with a CVSS score of 6.8, published 8 October 2026.
Which products and versions are affected?
Indico before 3.3.13; indico (PyPI) < 3.3.13, ECOSYSTEM:introduced=0,fixed=3.3.13.
Is there a fix for CVE-2026-107394?
Yes. indico (PyPI): upgrade to 3.3.13 or later. Until then: If Indico is not hosted on cloud platforms (such as AWS) that expose sensitive metadata without authentication, the risk is limited. Additionally, restrict trusted event organizers or configure HTTP proxy environment variables (`http_proxy` and `https_proxy` on both indico-uwsgi and indico-celery services) to restrict outgoing requests to approved destinations. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-107394 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-107394?
Check whether you run Indico or indico (PyPI) 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.

How to fix

  • indico (PyPI): upgrade to 3.3.13 or later
    pip install "indico>=3.3.13"

If Indico is not hosted on cloud platforms (such as AWS) that expose sensitive metadata without authentication, the risk is limited. Additionally, restrict trusted event organizers or configure HTTP proxy environment variables (`http_proxy` and `https_proxy` on both indico-uwsgi and indico-celery services) to restrict outgoing requests to approved destinations.

Technical details

An incomplete SSRF validation in Indico allows attackers to craft URLs that evade the previous fix (CVE-2026-25738) and reach local or restricted targets. The vulnerability requires authenticated access as an event organizer to reach endpoints where SSRF can be exploited. An attacker with organizer privileges can craft specially formatted URLs to access localhost or cloud metadata endpoints that would normally be blocked.

Affected products

  • Indico Indico before 3.3.13

Identifiers

  • CVE-2026-107394
  • GHSA-2v95-h47v-g4x9
  • PYSEC-2026-4225

Timeline

  • 2026-10-08: advisory

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.