Indico is an event management system that uses Flask-Multipass, a multi-backend authentication system for Flask. Versions prior to 3.3.10 are vulnerable to server-side request forgery. Indico makes outgoing requests to user-provides URLs in various places. This is mostly intentional and part of Indico's functionality but is never intended to let users access "special" targets such as localhost or cloud metadata endpoints. Users should upgrade to version 3.3.10 to receive a patch. Those who do not have IPs that expose sensitive data without authentication (typically because they do not host Indico on AWS) are not affected. Only event organizers can access endpoints where SSRF could be used to actually see the data returned by such a request. For those who trust their event organizers, the risk is also very limited. For additional security, both before and after patching, one may also use the common proxy-related environment variables (in particular http_proxy and https_proxy) to force outgoing requests to go through a proxy that limits requests in whatever way you deem useful/necessary. These environment variables would need to be set both on the indico-uwsgi and indico-celery services.
CVE-2026-25738
This medium-severity CVE scores 4.3 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(medium)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
February 19, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Aug 9, 2026Server-Side Request Forgery (SSRF) in multiple places · Advisory · indico/indico · GitHub
https://github.com/indico/indico/security/advisories/GHSA-f47c-3c5w-v7p4v3.3.10
Patch available: indico/indico v3.3.10
https://github.com/indico/indico/releases/tag/v3.3.10commit 70d341826116 (indico/indico)
Patch available: indico/indico v3.3.10 (contains commit 70d341826116)
https://github.com/indico/indico/commit/70d341826116fac5868719a6133f2c26d9345137Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| indico | 0.98-rc1 ... 3.3.9 (97 versions) | 3.3.10 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 25× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 20:20 UTCOSV refresh
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 23:23 UTCOSV refresh
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
Show 30 moreShow fewer
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 09:34 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 01:45 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 08:46 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 09:31 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 09:10 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 21:25 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 03:26 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 20:08 UTCEG score recompute
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 13:26 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-25738?
When was CVE-2026-25738 disclosed?
Is CVE-2026-25738 actively exploited?
What is the CVSS score of CVE-2026-25738?
How do I remediate CVE-2026-25738?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25738
Is Your Infrastructure Affected by CVE-2026-25738?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.