CVE-2026-108388GHSA-p9vj-86c7-h7q3
Indico legacy contribution export cache poisoning discloses restricted metadata
indico indico
CVSS
3.5LowExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.26%Chance of exploitation activity in the next 30 days, higher than 16% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed inNone listedNo source names a fixed version. Check the vendor advisory below
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
Indico is a feature-rich event management system. Indico 3.3.3 through 3.3.13 incorrectly uses the ambient web-session user instead of the user supplied to Contribution.can_manage when checking inherited event contribution-management permission. A low-privileged user can induce a privileged user to request a crafted legacy contribution export and cause speaker or author email addresses and contribution access-control entries to be stored in an API cache entry retrievable with less privilege. This issue was fixed in Indico 3.3.14.
Text from CVE List
Affected versions 1
- indicoaffected: >= 3.3.3, < 3.3.14CVE List
References 4
- github.com/indico/indico/commit/0e71da31fc21d0ed0ce687cce5b745ba2fad0b92Fixvia CVE List
- github.com/indico/indico/commit/5985cfa65a3441b7d3ca4ef1a9dc177c82ea0f26Fixvia CVE List
- github.com/indico/indico/releases/tag/v3.3.14Fixvia CVE List
- github.com/indico/indico/security/advisories/GHSA-p9vj-86c7-h7q3Advisoryvia CVE List