# CVE-2026-25738: Indico has Server-Side Request Forgery (SSRF) in multiple places

Source: https://junglewise.ai/threats/cve-2026-25738-indico-has-server-side-request-forgery-ssrf-in-multiple-places  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-02-19  
License: CC BY 4.0 with a link back

CVE-2026-25738 · Severity: medium · CVSS 4 · Published 2026-02-19

Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. Versions prior to 3.3.10 are vulnerable to server-side request forgery. Indico makes outgoing requests to user-provides URLs in various places. This is mostly intentional and part of Indico's functionality but is never intended to let users access "special" targets such as localhost or cloud metadata endpoints. Users should upgrade to version 3.3.10 to receive a patch. Those who do not have IPs that expose sensitive data without authentication (typically because they do not host Indico on AWS) are not affected. Only event organizers can access endpoints where SSRF could be used to actually see the data returned by such a request. For those who trust their event organizers, the risk is also very limited. For additional security, both before and after patching, one may 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.

Technologies: [indico (PyPI)](https://junglewise.ai/threats/technologies/indico). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2026-25738 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-25738 being exploited in the wild.

**How severe is CVE-2026-25738?** Medium severity, with a CVSS score of 4, published 19 February 2026.

**Which products and versions are affected?** indico (PyPI) ECOSYSTEM:introduced=0,fixed=3.3.10.

**Is there a fix for CVE-2026-25738?** Yes. indico (PyPI): upgrade to 3.3.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-25738?** Check whether you run 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.10 or later

  ```sh
  pip install "indico>=3.3.10"
  ```


## Affected products

- indico (PyPI) ECOSYSTEM:introduced=0,fixed=3.3.10

## Identifiers

- CVE-2026-25738
- GHSA-f47c-3c5w-v7p4
- PYSEC-2026-2181

## Related threats

- [Indico Cross-Site-Scripting in minutes editor](https://junglewise.ai/threats/cve-2026-107397-indico-cross-site-scripting-in-minutes-editor)
- [Indico cross-site scripting in link fields](https://junglewise.ai/threats/cve-2026-107396-indico-cross-site-scripting-in-link-fields)
- [Indico missing access check in legacy session export API](https://junglewise.ai/threats/cve-2026-107395-indico-missing-access-check-in-legacy-session-export-api)
- [Indico incomplete SSRF check in URL validation](https://junglewise.ai/threats/cve-2026-107394-indico-incomplete-server-side-request-forgery-ssrf-check)
- [PYSEC-2026-1461 - Indico vulnerable to Cross-Site Scripting via LaTeX math code](https://junglewise.ai/threats/cve-2025-59035-indico-vulnerable-to-cross-site-scripting-via-latex-math-code)