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 39 of 51
Current
SeverityCVECVSS
HIGHCVE-2026-617887.4
HIGHCVE-2026-772948.1
HIGHCVE-2026-835917.2
HIGHCVE-2026-890327.7
MEDIUMCVE-2026-1005285.4
MEDIUMCVE-2026-1005254.3
MEDIUMCVE-2026-1005265.3
MEDIUMCVE-2026-1005296.4
MEDIUMCVE-2026-1005335.3
MEDIUMCVE-2026-1005366.5
LOWCVE-2026-1005373.1
MEDIUMCVE-2026-1005386.5
LOWCVE-2026-1005392.6
MEDIUMCVE-2026-1005406.8
HIGHCVE-2026-1005437.5
MEDIUMCVE-2026-1005475.5
MEDIUMCVE-2026-1005485.3
HIGHCVE-2026-1005518.3
MEDIUMCVE-2026-1005544.2
HIGHCVE-2026-1005557.1

Page 39 of 51