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 16 of 16
Current
Severity CVE CVSS
CRITICAL CVE-2026-55615 -
CRITICAL GHSA-vjc7-jrh9-9j86 10.0
MEDIUM CVE-2026-55438 5.8
MEDIUM CVE-2026-55437 5.4
HIGH CVE-2026-55436 7.4
HIGH CVE-2026-55431 7.7
HIGH CVE-2026-26193 7.3
HIGH CVE-2026-26192 7.3
HIGH CVE-2025-46719 -
MEDIUM CVE-2025-46571 -
HIGH CVE-2026-53518 8.1
CRITICAL CVE-2026-59706 9.3
MEDIUM CVE-2026-15044 6.3
MEDIUM CVE-2026-56359 5.4
HIGH CVE-2026-59257 8.8
HIGH CVE-2026-59261 7.1
UNKNOWN CVE-2026-59821 -

Page 16 of 16