Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
6.5
Indico Event Series Management API Allows Unauthorized Access
CVE-2026-28352
GHSA-rfpp-2hgm-gp5v
Summary
Indico's event series management API doesn't check who's accessing it, which means anyone can see basic details about events in a series, delete the series, or modify its settings. Update to Indico 3.3.11 as soon as possible to fix this. As a temporary solution, you can restrict access to the API endpoint in your web server settings.
What to do
- Update indico to version 3.3.11.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| – | indico | <= 3.3.11 | 3.3.11 |
| cern | indico | <= 3.3.11 | – |
Original title
Indico has a missing access check in the event series management API
Original description
### Impact
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: This just removes the series metadata, ie (if enabled) the links between events in the same series and the lecture series number in the event title
- Modifying an existing event series: Just like for deleting, it would only allow to toggle the metadata display. It could also be used to set an event title pattern for the series, but this is only used when cloning an event from that series.
That 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.
### Patches
Developers should to update to [Indico 3.3.11](https://github.com/indico/indico/releases/tag/v3.3.11) as soon as possible.
See [the docs](https://docs.getindico.io/en/stable/installation/upgrade/) for instructions on how to update.
### Workarounds
- Developers can configure their webserver to restrict access to the series management API endpoint
### For more information
If there are any questions or comments about this advisory:
- Open a thread in [our forum](https://talk.getindico.io/)
- Email Indico privately at [[email protected]](mailto:[email protected])
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: This just removes the series metadata, ie (if enabled) the links between events in the same series and the lecture series number in the event title
- Modifying an existing event series: Just like for deleting, it would only allow to toggle the metadata display. It could also be used to set an event title pattern for the series, but this is only used when cloning an event from that series.
That 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.
### Patches
Developers should to update to [Indico 3.3.11](https://github.com/indico/indico/releases/tag/v3.3.11) as soon as possible.
See [the docs](https://docs.getindico.io/en/stable/installation/upgrade/) for instructions on how to update.
### Workarounds
- Developers can configure their webserver to restrict access to the series management API endpoint
### For more information
If there are any questions or comments about this advisory:
- Open a thread in [our forum](https://talk.getindico.io/)
- Email Indico privately at [[email protected]](mailto:[email protected])
nvd CVSS3.1
6.5
Vulnerability type
CWE-306
Missing Authentication for Critical Function
- https://nvd.nist.gov/vuln/detail/CVE-2026-28352
- https://github.com/advisories/GHSA-rfpp-2hgm-gp5v
- https://github.com/indico/indico/releases/tag/v3.3.11 Product Release Notes
- https://github.com/indico/indico/security/advisories/GHSA-rfpp-2hgm-gp5v Mitigation Patch Vendor Advisory
Published: 1 Mar 2026 · Updated: 13 Mar 2026 · First seen: 6 Mar 2026