AI security incident: Indico has Server-Side Request Forgery (SSRF) in multiple places (GHSA-f47c-3c5w-v7p4)
Impact Indico makes outgoing requests to user-provides URLs in various places. This is mostly intentional and part of Indico's functionality, but of course it is never intended to let you access "special" targets such as localhost or cloud metadata endpoints. ### Patches You should to update to [Indico 3.3.10](https://github.com/indico/indico/releases/tag/v3.3.10) as soon as possible. See [the docs](https://docs.getindico.io/en/stable/installation/upgrade/) for instructions on how to update. ### Workarounds If you do not have IPs that expose sensitive data without authentication (typically because you do not host Indico on AWS), this vulnerability doesn't impact you and you can ignore it (but please upgrade anyway).
Why This Is AI-Related
This advisory is part of the public incident archive, but the current source material uses limited explicit AI terminology, so the cited sources should be reviewed carefully when judging AI relevance and exposure.
- Explicit AI-specific signals are limited in the current source material, so use the cited advisory to validate scope during triage.
Affected Workflow
Review connectors, retrieval plugins, webhook targets, file access paths, and outbound network policies around AI services.
Likely Attack Path
The flaw creates an unauthorized path to fetch, read, or exfiltrate sensitive data from connected systems or local files.
Impact
The flaw can expose internal data, local files, or connected systems through AI workflow connectors and supporting services. Severity HIGH. Classification confidence 53%. Source channel GHSA.
Detection And Triage Signals
- Unexpected outbound requests from AI application components
- Access to internal metadata endpoints, local files, or restricted datasets
- Downloads or responses that contain internal documents, secrets, or embeddings
Recommended Response
- Confirm whether the affected component can reach internal metadata, local files, or connected data stores.
- Restrict outbound requests and sensitive data access paths until a patch or mitigation is in place.
- Inspect logs for unusual downloads, webhook calls, retrieval requests, or responses containing internal content.
Compliance And Business Impact
Data exposure creates direct confidentiality risk and can trigger incident notification, contractual, and regulatory obligations.
Sources
Want alerts like this in real time?
Get notified with incident context, likely impact, and response guidance.
Get Notified