CVE-2026-107394: Indico: Incomplete Server-Side Request Forgery (SSRF) check
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.
Published Oct 8, 2026
Affected packages
indico
- Ecosystem
- PyPI
- Affected
- < 3.3.13
- Fixed in
- 3.3.13
- Check
pip show indico
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 as soon as possible. See the docs 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
- Email us privately at [[email protected]](mailto:[email protected])
Credited to Fushuling, RacerZ-fighting.
References
- https://github.com/indico/indico/security/advisories/GHSA-2v95-h47v-g4x9
- https://nvd.nist.gov/vuln/detail/CVE-2026-107394
- https://github.com/indico/indico/pull/7573
- https://github.com/indico/indico/commit/44540e70ab4e20a12f14ddba5218a33749a86736
- https://github.com/indico/indico/releases/tag/v3.3.13
- https://github.com/advisories/GHSA-2v95-h47v-g4x9
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-107395
Indico: Missing access check in legacy session export API
medium4.3Oct 8, 2026CVE-2026-107396
Indico: Cross-Site-Scripting in link fields
medium5.4Oct 8, 2026CVE-2026-107397
Indico: Cross-Site-Scripting in minutes editor
medium4.4Oct 8, 2026CVE-2026-33046
Indico discloses local files resulting in Remote Code Execution through LaTeX injection
high7.7Mar 23, 2026CVE-2026-28352
Indico has a missing access check in the event series management API
medium6.5Mar 1, 2026CVE-2026-25738
Indico has Server-Side Request Forgery (SSRF) in multiple places
medium6.9Feb 17, 2026
