# CVE-2026-108388: Indico legacy contribution export cache poisoning discloses restricted metadata

> A low-privileged user can trick a privileged user into caching restricted metadata, allowing the attacker to read sensitive speaker and author information.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-p9vj-86c7-h7q3

## What is CVE-2026-108388?

CVE-2026-108388 is a low-severity vulnerability in indico, published on 13 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-108388?


## How do I fix CVE-2026-108388?

No fix has been published for CVE-2026-108388 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-108388 being exploited?

There is no known exploitation of CVE-2026-108388 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108388 and fix it if it is affected.

What it is: CVE-2026-108388 is a low-severity vulnerability in indico, published on 13 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-108388 in the wild and no public exploit code.

Affected product: indico. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-108388/ (Markdown: https://insights.sbomify.com/CVE-2026-108388/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-108388
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-108388
- OSV: https://osv.dev/vulnerability/CVE-2026-108388

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-108388/
Summaries are generated and may contain mistakes; the official description above is the record.