← Back
CVE-2025-53640
Information Disclosure in indico (CVE-2025-53640)
Summary
vulnerability in indico (CVE-2025-53640). Risk of unauthorized operations or information disclosure. Exploitable via ``ALLOW_PUBLIC_USER_SEARCH``. Mitigation: upgrade to `3.3.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-53640** has been found in indico.
Attackers can target a specific entry point like ``ALLOW_PUBLIC_USER_SEARCH`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade indico to **3.3.7** or later.
If unsure, ask your IT team or search "indico CVE-2025-53640" on the vendor's site.
CVE-2025-53640 (indico) — CWE-200 /
Attack surface: `ALLOW_PUBLIC_USER_SEARCH`
Patched: `3.3.7` — apply immediately
Workaround: It is possible to restrict access to the affected endpoints (e.g.
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
**information disclosure** (CWE-200) exists in indico. Attackers reach the vulnerable code path via ``ALLOW_PUBLIC_USER_SEARCH`` without authentication.
📍 Affected scope
indico — . Attack surface: `ALLOW_PUBLIC_USER_SEARCH`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.3.7**.
🛡️ Workaround
Workaround: It is possible to restrict access to the affected endpoints (e.g.
🔍 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'indico' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `indico` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
It is possible to restrict access to the affected endpoints (e.g.パッチが適用されるまでの応急処置として、It is possible to restrict access to the affected endpoints (e.g. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade indico to 3.3.7ステージング環境で 3.3.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
indico
[{"type":"ECOSYSTEM","events":[{"introduced":"2.2"},{"fixed":"3.3.7"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-53640
- advisory https://github.com/advisories/GHSA-q28v-664f-q6wj
- package https://github.com/indico/indico
- package https://pypi.org/project/indico
- web https://github.com/indico/indico/security/advisories/GHSA-q28v-664f-q6wj
- web https://github.com/indico/indico/pull/6936/commits/f8583557a3da56aeea8857ae69bf17c9066c95c1
- web https://docs.getindico.io/en/stable/config/settings/#ALLOW_PUBLIC_USER_SEARCH
- web https://docs.getindico.io/en/stable/installation/upgrade
- web https://github.com/indico/indico/releases/tag/v3.3.7
- web https://www.vicarius.io/vsociety/posts/cve202553640-detect-indico-vulnerability
- web https://www.vicarius.io/vsociety/posts/cve202553640-mitigate-indico-vulnerability