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.

317
Total CVEs
16
Pages
Page 8 of 16
Current
Severity CVE CVSS
HIGH GHSA-w47f-j8rh-wx87 -
LOW CVE-2026-6597 2.7
MEDIUM CVE-2026-41495 5.3
HIGH CVE-2026-41266 7.5
MEDIUM GHSA-wg4g-395p-mqv3 4.3
MEDIUM CVE-2026-7141 5.6
UNKNOWN CVE-2026-41686 -
MEDIUM CVE-2026-3345 6.5
CRITICAL CVE-2026-7482 9.1
MEDIUM CVE-2026-41358 5.4
MEDIUM GHSA-93rg-2xm5-2p9v -
MEDIUM GHSA-cqmh-pcgr-q42f 5.5
HIGH CVE-2026-44504 -
MEDIUM CVE-2026-44558 5.4
HIGH GHSA-8g7g-hmwm-6rv2 8.3
CRITICAL CVE-2026-44211 9.6
MEDIUM CVE-2026-42282 4.3
MEDIUM CVE-2026-44337 6.3
LOW CVE-2026-8026 3.7
HIGH CVE-2026-45134 7.1

Page 8 of 16