GHSA-2v95-h47v-g4x9: SSRF
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 httpproxy and httpsproxy) 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 indico-team@cern.ch
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/indicoto a version that resolves this vulnerability.Fixed in 3.3.13 - Upgrade
Upgrade
Indicoto a version that resolves this vulnerability.Fixed in 3.3.13 - Compensating control
Set the http_proxy and https_proxy environment variables on both the indico-uwsgi and indico-celery services to force outgoing requests through a proxy that limits requests as needed.
Event History
Frequently Asked Questions
Who can exploit this issue?
Only event organizers can access the endpoints where the SSRF behavior can be used to view data returned by an outgoing request. An attacker would need event-organizer access and the ability to provide a crafted URL.
When is the practical risk highest?
Risk is highest when the Indico host can reach IP addresses exposing sensitive data without authentication, such as cloud metadata endpoints. The advisory notes that this is typically less relevant when Indico is not hosted on AWS.
What should we do to remediate it?
Update Indico to version 3.3.13 as soon as possible. If immediate patching is not possible, exposure is limited if you trust event organizers and do not have reachable unauthenticated IP-based services containing sensitive data.