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 38 of 51
Current
SeverityCVECVSS
MEDIUMCVE-2026-958156.3
MEDIUMCVE-2026-772495.3
HIGHCVE-2026-77247-
HIGHCVE-2026-772628.6
MEDIUMCVE-2026-772685.5
HIGHCVE-2026-772597.7
MEDIUMCVE-2026-772666.5
MEDIUMCVE-2026-772696.5
HIGHCVE-2026-77257-
HIGHCVE-2026-772558.6
HIGHCVE-2026-772537.1
HIGHCVE-2026-772467.4
HIGHCVE-2026-772488.6
CRITICALCVE-2026-772549.1
HIGHCVE-2026-77256-
HIGHCVE-2026-566767.4
MEDIUMCVE-2026-345105.3
HIGHCVE-2026-441137.7
MEDIUMCVE-2026-441175.8
HIGHGHSA-g28h-2cmm-rj9x7.5

Page 38 of 51