Data Leakage
Data leakage in AI systems happens at three layers. At training time, models can memorise rare strings from their corpus — phone numbers, passwords, API keys committed to public code — and an attacker who knows the right context can prompt the model to regurgitate them. At inference time, applications often pass sensitive context to third-party APIs (OpenAI, Anthropic, Bedrock) without redaction; this content is then potentially logged, retained, or used to improve future models depending on the vendor's terms. At the application layer, multi-tenant deployments routinely leak across users when caching, logging, or vector-store indexing is misconfigured. Indirect prompt injection compounds all three by giving an attacker a way to ask the model to repeat what it should not. Defenses: PII redaction in prompts and outputs, differential privacy in training, vendor data-use review, and strict tenant boundaries in shared infrastructure.
| Severity | CVE | Headline | Package | CVSS |
|---|---|---|---|---|
| UNKNOWN | CVE-2026-120630 | CrewAI: SSRF guard parser differential enables internal access | CrewAI | - |
| MEDIUM | CVE-2026-115289 | Elastic APM Server: config mixup leaks other services' settings | 4.3 | |
| HIGH | CVE-2026-115714 | Elastic Docker images: compromised eMudhra CAs enable TLS MITM | 7.4 | |
| HIGH | CVE-2026-121561 | Label Studio: SSRF in export leaks internal data, API token | label-studio | 7.7 |
Page 51 of 51