Skip to content

Indico has a missing access check in the event series management API

Moderate severity GitHub Reviewed Published Feb 27, 2026 in indico/indico • Updated Mar 1, 2026

Package

indico (pip)

Affected versions

< 3.3.11

Patched versions

3.3.11

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 as soon as possible.
See the docs 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:

References

@ThiefMaster ThiefMaster published to indico/indico Feb 27, 2026
Published by the National Vulnerability Database Feb 27, 2026
Published to the GitHub Advisory Database Mar 1, 2026
Reviewed Mar 1, 2026
Last updated Mar 1, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(11th percentile)

Weaknesses

Missing Authentication for Critical Function

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. Learn more on MITRE.

CVE ID

CVE-2026-28352

GHSA ID

GHSA-rfpp-2hgm-gp5v

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.