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 34 of 51
Current
SeverityCVECVSS
MEDIUMCVE-2026-893325.5
HIGHCVE-2026-591488.8
MEDIUMCVE-2026-879165.3
MEDIUMCVE-2026-905336.5
MEDIUMCVE-2026-905346.5
HIGHCVE-2026-907697.7
LOWCVE-2026-905293.5
MEDIUMCVE-2026-571156.5
HIGHCVE-2026-571268.5
MEDIUMCVE-2026-571284.3
HIGHCVE-2026-571297.5
HIGHCVE-2026-571308.1
HIGHCVE-2026-909438.7
HIGHCVE-2026-571197.5
CRITICALCVE-2026-571279.8
CRITICALCVE-2026-571319.8
HIGHCVE-2026-571328.2
CRITICALCVE-2026-571459.1
MEDIUMCVE-2026-127634.2
MEDIUMCVE-2026-127656.5

Page 34 of 51