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.

175
Total CVEs
9
Pages
Page 5 of 9
Current
Severity CVE CVSS
HIGH CVE-2025-61917 7.7
CRITICAL CVE-2026-25052 9.9
UNKNOWN CVE-2025-11203 -
MEDIUM CVE-2026-30886 6.5
MEDIUM CVE-2026-28277 6.8
LOW CVE-2026-25211 3.2
MEDIUM CVE-2025-68492 4.2
HIGH GHSA-9726-w42j-3qjr -
HIGH CVE-2025-65958 8.5
HIGH CVE-2025-64104 7.3
MEDIUM CVE-2025-51481 6.6
MEDIUM CVE-2025-6211 6.5
HIGH CVE-2025-6209 7.5
MEDIUM CVE-2025-3044 5.3
HIGH CVE-2025-3046 7.5
CRITICAL CVE-2025-1793 9.8
HIGH CVE-2025-47783 -
CRITICAL CVE-2025-32428 -
HIGH CVE-2025-46417 -
MEDIUM CVE-2024-7045 4.3

Page 5 of 9