Quick answers
- Is CVE-2026-107395 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107395 being exploited in the wild.
- How severe is CVE-2026-107395?
- Medium severity, with a CVSS score of 4.3, published 8 October 2026.
- Which products and versions are affected?
- Indico before 3.3.13; indico (PyPI) < 3.3.13, ECOSYSTEM:introduced=0,fixed=3.3.13.
- Is there a fix for CVE-2026-107395?
- Yes. indico (PyPI): upgrade to 3.3.13 or later. Until then: Restrict access to the event itself to limit who can interact with any APIs relating to that event. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107395 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-107395?
- Check whether you run Indico or indico (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- indico (PyPI): upgrade to 3.3.13 or later
pip install "indico>=3.3.13"
Restrict access to the event itself to limit who can interact with any APIs relating to that event.
Technical details
The legacy session export API endpoint fails to perform proper authorization checks on restricted sessions. An authenticated attacker with access to an event can call the API to retrieve metadata from sessions within that event that they are not authorized to view. The vulnerability requires low-privilege authentication and network access to the Indico instance, allowing information disclosure with low confidentiality impact.
Affected products
- Indico Indico before 3.3.13
Identifiers
- CVE-2026-107395
- GHSA-6p4f-j8j6-463q
- PYSEC-2026-4226
Timeline
- 2026-08-25: disclosed
- 2026-08-25: patched: Fix released in version 3.3.13
- 2026-10-08: advisory