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 47 of 51
Current
SeverityCVECVSS
HIGHCVE-2026-1124088.1
HIGHCVE-2026-1141358.8
MEDIUMCVE-2026-1137244.5
HIGHCVE-2026-1145107.1
HIGHCVE-2026-1155138.7
CRITICALCVE-2026-107685-
HIGHCVE-2026-568358.3
HIGHCVE-2026-568347.5
HIGHCVE-2026-568337.5
HIGHCVE-2026-571147.2
CRITICALCVE-2026-571169.8
HIGHCVE-2026-571448.8
HIGHCVE-2026-571467.5
MEDIUMCVE-2026-554655.3
HIGHCVE-2026-730547.5
MEDIUMCVE-2026-736305.8
MEDIUMCVE-2026-730495.8
MEDIUMGHSA-xp3q-r38w-vgqm5.8
MEDIUMCVE-2026-1158866.5
MEDIUMCVE-2026-115883-

Page 47 of 51