CVE-2026-28352

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
• Email Indico privately at [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.

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

CVE-2026-28352 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.3.11); upgrading removes the vulnerable code path.

Kodem intelligence

Developers should to update to Indico 3.3.11 as soon as possible.
See the docs for instructions on how to update.

1. What is CVE-2026-28352? CVE-2026-28352 is a medium-severity missing authentication for critical function vulnerability in indico (pip), affecting versions < 3.3.11. It is fixed in 3.3.11. A critical operation is accessible without requiring any authentication.
2. How severe is CVE-2026-28352? CVE-2026-28352 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of indico are affected by CVE-2026-28352? indico (pip) versions < 3.3.11 is affected.
4. Is there a fix for CVE-2026-28352? Yes. CVE-2026-28352 is fixed in 3.3.11. Upgrade to this version or later.
5. Is CVE-2026-28352 exploitable, and should I be worried? Whether CVE-2026-28352 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-28352 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-28352? Upgrade indico to 3.3.11 or later.