CVE-2026-107394: Indico Incomplete Server-Side Request Forgery (SSRF) Vulnerability

MODERATE
Advisory Identifier: GHSA-2v95-h47v-g4x9
CVSS 6.8
CWE-918
Published
Advisory Summary

CVE-2026-107394 is a MODERATE (CVSS 6.8) incomplete server-side request forgery (ssrf) vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Indico libraries in the PyPI ecosystem. The issue involves incomplete server-side request forgery (ssrf) check. Remediation is available by upgrading affected packages to version 3.3.13.

CVE-2026-107394 at a Glance

CVE Identifier CVE-2026-107394
GHSA Identifier GHSA-2v95-h47v-g4x9
Severity MODERATE
CVSS v3.1 Base Score 6.8
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Indico
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 6.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-107394

To remediate this vulnerability, upgrade all affected Indico dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

indico fixed: 3.3.13
pip install indico>=3.3.13
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show indico

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-107394, inspect your installed packages using pip:

pip show indico

Analyze the terminal output to locate any version of Indico in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.3.13), your application is affected.

Note: The pip show indico command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Indico, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Indico makes outgoing requests to user-provides URLs in various places. This is mostly intentional and part of Indico's functionality, but of course it is never intended to let you access "special" targets such as localhost or cloud metadata endpoints. The previous fix (CVE-2026-25738) did not cover an edge case so it was still possible to craft a URL that pointed to a local target but was accepted as valid by Indico. ### Patches You should to update to [Indico 3.3.13](https://github.com/indico/indico/releases/tag/v3.3.13) as soon as possible. See [the docs](https://docs.getindico.io/en/stable/installation/upgrade/) for instructions on how to update. ### Workarounds If you do not have IPs that expose sensitive data without authentication (typically because you do not host Indico on AWS), this vulnerability doesn't impact you and you can ignore it (but please upgrade anyway). Also, only event organizers can access endpoints where SSRF could be used to actually see the data returned by such a request. So if you trust your event organizers, the risk is also very limited. For additional security, both before and after patching, you could 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. Please note that setting up such a proxy is not something we can help you with. ### For more information If you have any questions or comments about this advisory: - Open a thread in [our forum](https://talk.getindico.io/) - Email us privately at [indico-team@cern.ch](mailto:indico-team@cern.ch)

CVE-2026-107394 Affected Indico Versions

1 component(s)
Fixed Versions:
3.3.13
Product / Package Ecosystem Affected Versions Fixed Version
indico
PyPI
< 3.3.13
3.3.13

References

Frequently Asked Questions

What is CVE-2026-107394?
CVE-2026-107394 is a security vulnerability in Indico involving Incomplete Server-Side Request Forgery (SSRF) check under CWE-918: Server-Side Request Forgery (SSRF).
Which Indico versions are affected?
Affected versions include releases prior to 3.3.13 across affected packages: indico.
What version fixes CVE-2026-107394?
Upgrading to 3.3.13 (or the latest patched release for your respective branch) resolves the vulnerability.
Is indico affected?
Yes, indico is affected in releases prior to 3.3.13. Upgrade your dependency to 3.3.13 or later.
What is the CVSS score of CVE-2026-107394?
CVE-2026-107394 has a CVSS v3.1 base score of 6.8 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N.
What CWE is associated with CVE-2026-107394?
CVE-2026-107394 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check PyPI dependencies for CVE-2026-107394?
Run the dependency tree command: 'pip show indico'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2v95-h47v-g4x9",
  "modified" : "2026-10-08T22:09:55Z",
  "published" : "2026-10-08T22:09:55Z",
  "aliases" : [ "CVE-2026-107394" ],
  "summary" : "Indico: Incomplete Server-Side Request Forgery (SSRF) check",
  "details" : "### Impact\nIndico makes outgoing requests to user-provides URLs in various places. This is mostly intentional and part of Indico's functionality, but of course it is never intended to let you access \"special\" targets such as localhost or cloud metadata endpoints. The previous fix (CVE-2026-25738) did not cover an edge case so it was still possible to craft a URL that pointed to a local target but was accepted as valid by Indico.\n\n### Patches\nYou should to update to [Indico 3.3.13](https://github.com/indico/indico/releases/tag/v3.3.13) as soon as possible.\nSee [the docs](https://docs.getindico.io/en/stable/installation/upgrade/) for instructions on how to update.\n\n### Workarounds\nIf you do not have IPs that expose sensitive data without authentication (typically because you do not host Indico on AWS), this vulnerability doesn't impact you and you can ignore it (but please upgrade anyway).\nAlso, only event organizers can access endpoints where SSRF could be used to actually see the data returned by such a request. So if you trust your event organizers, the risk is also very limited.\n\nFor additional security, both before and after patching, you could 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. Please note that setting up such a proxy is not something we can help you with.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n- Open a thread in [our forum](https://talk.getindico.io/)\n- Email us privately at [indico-team@cern.ch](mailto:indico-team@cern.ch)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "indico"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.3.13"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/indico/indico/security/advisories/GHSA-2v95-h47v-g4x9"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-107394"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/indico/indico/pull/7573"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/indico/indico/commit/44540e70ab4e20a12f14ddba5218a33749a86736"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/indico/indico"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/indico/indico/releases/tag/v3.3.13"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-08T22:09:55Z",
    "nvd_published_at" : "2026-10-08T20:17:34Z"
  }
}