Categories
CVE-2026-107395 medium CVSS 4.3

Vulnerability in indico (CVE-2026-107395)

Summary

Vulnerability in indico (CVE-2026-107395). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.3.13 or later.

Original description

The description as published by the source.

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:

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-107395 has been found in indico.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade indico to 3.3.13 or later.
If unsure, ask your IT team or search "indico CVE-2026-107395" on the vendor's site.

CVE-2026-107395 (indico) — CWE-862 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.3.13 — apply immediately
Workaround: Restrict access to the event itself
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-862) exists in indico.

📍 Affected scope

Check the vendor advisory for the affected versions of indico.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.3.13.

🛡️ Workaround

Workaround: Restrict access to the event itself

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'indico' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'indico' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で indico を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    Restrict access to the event itself

    パッチが適用されるまでの応急処置として、Restrict access to the event itself を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade indico to 3.3.13

    ステージング環境で 3.3.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip indico
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.13"}]}]
PyPI indico
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.13"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details