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 37 of 51
Current
SeverityCVECVSS
MEDIUMCVE-2026-551796.5
MEDIUMCVE-2026-598164.3
MEDIUMCVE-2026-466504.4
HIGHCVE-2026-552107.4
HIGHCVE-2026-598147.6
HIGHCVE-2026-894127.2
MEDIUMCVE-2026-616125.7
MEDIUMCVE-2026-793154.7
MEDIUMCVE-2026-933446.5
MEDIUMCVE-2026-857095.3
HIGHCVE-2026-77274-
HIGHCVE-2026-772587.7
MEDIUMCVE-2026-772655.9
MEDIUMCVE-2026-772706.5
MEDIUMCVE-2026-772506.1
HIGHCVE-2026-77260-
HIGHCVE-2026-772617.1
HIGHCVE-2026-772438.8
MEDIUMCVE-2026-772526.5
HIGHCVE-2026-77251-

Page 37 of 51