CVE-2026-107395: Indico: Missing access check in legacy session export API

Published Oct 8, 2026
·
Updated

Impact A legacy API to retrieve session details could be misused to retrieve metadata (such as title, description and conveners) of a restricted session within without having access to that session, as long as the event itself was accessible.

Patches You should to update to Indico 3.3.13 as soon as possible. See the docs for instructions on how to update.

Workarounds Restrict access to the event itself

For more information If you have any questions or comments about this advisory:

- Open a thread in our forum - Email us privately at indico-team@cern.ch

Other sources

Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. Prior to 3.3.13, an authenticated user can misuse the legacy session export API to retrieve details for a restricted session without access to that session, as long as the containing event is accessible. The missing access check can disclose session metadata such as the title, description, and conveners. This issue is fixed in version 3.3.13.

— MITRE

Affected Software

2 affected componentsFixes available
cern Indico<3.3.13
pip/indico<3.3.13
3.3.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/indico to a version that resolves this vulnerability.

    Fixed in 3.3.13
  2. Upgrade

    Upgrade Indico to a version that resolves this vulnerability.

    Fixed in 3.3.13
  3. Compensating control

    Restrict access to the event itself.

Event History

Oct 8, 2026
CVE Published
via MITRE·07:57 PM
Data Sourced
via MITRE·07:57 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·10:09 PM
Data Sourced
via GitHub·10:09 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Who can exploit this issue?

Any authenticated Indico user can exploit it if they can access the event containing a restricted session. They do not need access to the restricted session itself.

2

What information could be exposed?

The legacy session export API can disclose metadata for restricted sessions, including the session title, description, and conveners. The provided information does not indicate exposure of session content or modification capabilities.

3

Which deployments are affected?

Indico versions prior to 3.3.13 are affected. The issue concerns deployments where authenticated users can access an event that contains restricted sessions.

4

How can this be remediated?

Upgrade Indico to version 3.3.13, which includes the fix for the missing access check in the legacy session export API.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203