{"answers":{"affected":"3 open source packages ship an affected version, including indico. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25738 in the wild and no public exploit code.","fix":"Upgrade indico to 3.3.10 or later.","what":"CVE-2026-25738 is a medium-severity server-side request forgery vulnerability in indico, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25738 and fix it if it is affected.\n\nWhat it is: CVE-2026-25738 is a medium-severity server-side request forgery vulnerability in indico, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25738 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- indico (PyPI): affected all versions; fixed in 3.3.10\n- indico (PyPI): affected all versions; fixed in 3.3.10\n- indico (PyPI): affected all versions; fixed in 3.3.10\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25738/ (Markdown: https://insights.sbomify.com/CVE-2026-25738/index.md)","id":"CVE-2026-25738","markdown":"https://insights.sbomify.com/CVE-2026-25738/index.md","name":"CVE-2026-25738","record":{"aliases":["GHSA-f47c-3c5w-v7p4","PYSEC-2026-2181"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Indico event management","requires_auth":"none","summary":"Attackers can exploit SSRF in Indico to access internal services or cloud metadata, primarily affecting deployments on cloud infrastructure like AWS.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"indico","vendor":"cern"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Indico has Server-Side Request Forgery (SSRF) in multiple places","id":"CVE-2026-25738","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Indico affected by Cross-Site-Scripting via material uploads","id":"CVE-2026-25739"},"packages":[{"ecosystem":"PyPI","fixed":["3.3.10"],"introduced":["0"],"last_affected":[],"package":"indico","purl":null,"source":"GHSA-f47c-3c5w-v7p4"},{"ecosystem":"PyPI","fixed":["3.3.10"],"introduced":["0"],"last_affected":[],"package":"indico","purl":"pkg:pypi/indico","source":"GHSA-f47c-3c5w-v7p4"},{"ecosystem":"PyPI","fixed":["3.3.10"],"introduced":["0"],"last_affected":[],"package":"indico","purl":"pkg:pypi/indico","source":"PYSEC-2026-2181"}],"prev":{"headline":"Budibase Arbitrary File Upload Leading to Multiple Critical Vulnerabilities (SSRF, Stored XSS)","id":"CVE-2026-25737"},"products":["indico"],"published":"2026-02-19","related":[{"cvss_score":7.7,"headline":"Indico discloses local files resulting in Remote Code Execution through LaTeX injection","id":"CVE-2026-33046","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":7.5,"headline":"Indico Tampering with links (e.g. password reset) in sent emails","id":"CVE-2021-30185","kev_date_added":null,"published":"2021-04-07"},{"cvss_score":6.5,"headline":"Indico missing access check in event series management API","id":"CVE-2026-28352","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":5.4,"headline":"Indico affected by Cross-Site-Scripting via material uploads","id":"CVE-2026-25739","kev_date_added":null,"published":"2026-02-19"},{"cvss_score":5.4,"headline":"Cross-Site-Scripting via confirmation prompts","id":"CVE-2023-37901","kev_date_added":null,"published":"2023-07-21"},{"cvss_score":5.3,"headline":"Indico vulnerable to user enumeration via API endpoint","id":"CVE-2025-53640","kev_date_added":null,"published":"2025-07-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-19","vendors":["indico"]},"summary":"Attackers can exploit SSRF in Indico to access internal services or cloud metadata, primarily affecting deployments on cloud infrastructure like AWS.","url":"https://insights.sbomify.com/CVE-2026-25738/"}