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 35 of 51
Current
SeverityCVECVSS
MEDIUMCVE-2026-127665.4
MEDIUMCVE-2026-127676.5
MEDIUMCVE-2026-78845.4
MEDIUMCVE-2026-550936.1
MEDIUMCVE-2026-908184.3
MEDIUMCVE-2026-734976.5
HIGHCVE-2026-734967.7
HIGHCVE-2026-571128.3
HIGHCVE-2026-571348.2
HIGHCVE-2026-571357.6
CRITICALCVE-2026-571389.9
CRITICALCVE-2026-571409.4
HIGHCVE-2026-919337.1
HIGHCVE-2026-181107.5
HIGHCVE-2026-919297.1
HIGHCVE-2026-919307.5
HIGHCVE-2026-919348.8
HIGHCVE-2026-919358.3
HIGHCVE-2026-919377.5
HIGHCVE-2026-919387.1

Page 35 of 51