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 40 of 51
Current
SeverityCVECVSS
HIGHCVE-2026-1005578.3
MEDIUMCVE-2026-1005625.4
MEDIUMCVE-2026-1005635.4
MEDIUMCVE-2026-1005666.5
HIGHCVE-2026-1005678.2
HIGHCVE-2026-1005688.3
MEDIUMCVE-2026-1005695.5
LOWCVE-2026-1005733.3
MEDIUMCVE-2026-1005745.9
HIGHCVE-2026-1005758.8
MEDIUMCVE-2026-1005765.4
MEDIUMCVE-2026-1005776.3
MEDIUMCVE-2026-1005815.5
MEDIUMCVE-2026-1005826.5
MEDIUMCVE-2026-1005834.3
HIGHCVE-2026-1005888.3
HIGHCVE-2026-1005898.3
MEDIUMCVE-2026-1005926.3
MEDIUMCVE-2026-1005935.4
MEDIUMCVE-2026-1005946.5

Page 40 of 51