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

> An event organizer can bypass SSRF protections to read data from prohibited local targets via crafted URLs in Indico.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-2v95-h47v-g4x9, PYSEC-2026-4225

## What is CVE-2026-107394?

CVE-2026-107394 is a medium-severity server-side request forgery vulnerability in indico, published on 8 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. Prior to 3.3.13, the previous fix for CVE-2026-25738 did not cover an edge case, allowing an event organizer to submit a crafted URL that points to a prohibited local target but is accepted as valid by Indico. The organizer can read data returned by the target through affected Indico features. This issue is fixed in version 3.3.13.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-107394?

3 open source packages ship an affected version, including indico.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `indico` | PyPI | All versions | 3.3.13 |
| `indico` | PyPI | All versions | 3.3.13 |
| `indico` | PyPI | All versions | 3.3.13 |

## How do I fix CVE-2026-107394?

Upgrade indico to 3.3.13 or later.

## Is CVE-2026-107394 being exploited?

There is no known exploitation of CVE-2026-107394 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107394 and fix it if it is affected.

What it is: CVE-2026-107394 is a medium-severity server-side request forgery vulnerability in indico, published on 8 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107394 in the wild and no public exploit code.

Affected packages and fixed versions:
- indico (PyPI): affected all versions; fixed in 3.3.13
- indico (PyPI): affected all versions; fixed in 3.3.13
- indico (PyPI): affected all versions; fixed in 3.3.13

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107394/ (Markdown: https://insights.sbomify.com/CVE-2026-107394/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107394
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107394
- OSV: https://osv.dev/vulnerability/CVE-2026-107394

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107394/
Summaries are generated and may contain mistakes; the official description above is the record.