Low · CVSS 3.5CVE-2026-108388

Indico legacy contribution export cache poisoning discloses restricted metadataCVE-2026-108388

Answer in brief

CVE-2026-108388 records a Low severity (CVSS 3.5) vulnerability in Indico legacy contribution export cache poisoning discloses restricted metadata. The current sources do not mark it as known exploited. The current feed maps indico/indico (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 13, 2026Updated Oct 13, 2026Source checked Oct 13, 2026First seen by HOL Oct 13, 2026Material review Oct 13, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 3.5
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 3.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps indico/indico (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
indico/indicogeneric	>=3.3.3 <3.3.14	3.3.14

Recommended response

Check inventory. Check lockfiles and deployed manifests for indico/indico.
Review the reported fix. Update indico/indico to 3.3.14 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 13, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 13, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 13, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.