Attack Type

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.

1001
Total CVEs
51
Pages
Page 31 of 51
Current
SeverityCVECVSS
HIGHCVE-2026-728108.6
HIGHGHSA-7j72-f6wg-cxw68.6
HIGHCVE-2026-685868.6
HIGHCVE-2026-685878.6
HIGHCVE-2026-690867.7
MEDIUMCVE-2026-855786.5
HIGHCVE-2026-856667.5
HIGHCVE-2026-856867.5
MEDIUMCVE-2026-84476.1
MEDIUMCVE-2026-192996.5
HIGHCVE-2026-193007.5
MEDIUMCVE-2026-193016.5
MEDIUMCVE-2026-193026.5
HIGHCVE-2026-193047.7
HIGHCVE-2026-193057.5
HIGHCVE-2026-193067.7
MEDIUMCVE-2026-144706.5
MEDIUMCVE-2026-176215.4
MEDIUMCVE-2026-176226.5
HIGHCVE-2026-176277.1

Page 31 of 51