# CVE-2026-28352: Indico missing access check in event series management API

> Unauthenticated attackers can read, modify, or delete event series metadata in Indico due to a missing access check in the API.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Feb 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-rfpp-2hgm-gp5v, PYSEC-2026-2183

## What is CVE-2026-28352?

CVE-2026-28352 is a medium-severity missing authorization vulnerability in indico, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, 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. In versions prior to 3.3.11, the API endpoint used to manage event series is missing an access check, allowing unauthenticated/unauthorized access to this endpoint. The impact of this is limited to getting the metadata (title, category chain, start/end date) for events in an existing series, deleting an existing event series, and modifying an existing event series. This vulnerability does NOT allow unauthorized access to events (beyond the basic metadata mentioned above), nor any kind of tampering with user-visible data in events. Version 3.3.11 fixes the issue. As a workaround, use the webserver to restrict access to the series management API endpoint.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

3 open source packages ship an affected version, including indico. It affects 1 product.


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

Products: Cern Indico.

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

Upgrade indico to 3.3.11 or later.

## Is CVE-2026-28352 being exploited?

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

## Other vulnerabilities in indico

- [CVE-2026-33046](https://insights.sbomify.com/CVE-2026-33046/): Indico discloses local files resulting in Remote Code Execution through LaTeX injection (high 7.7)
- [CVE-2021-30185](https://insights.sbomify.com/CVE-2021-30185/): Indico Tampering with links (e.g. password reset) in sent emails (high 7.5)
- [CVE-2026-25738](https://insights.sbomify.com/CVE-2026-25738/): Indico has Server-Side Request Forgery (SSRF) in multiple places (medium 6.9)
- [CVE-2026-25739](https://insights.sbomify.com/CVE-2026-25739/): Indico affected by Cross-Site-Scripting via material uploads (medium 5.4)
- [CVE-2023-37901](https://insights.sbomify.com/CVE-2023-37901/): Cross-Site-Scripting via confirmation prompts (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28352 is a medium-severity missing authorization vulnerability in indico, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-28352 in the wild and no public exploit code.

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

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-28352/ (Markdown: https://insights.sbomify.com/CVE-2026-28352/index.md)
```

## Sources

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

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