Privacy Violation
Privacy is an unusual security category in AI because the data is often inside the model rather than next to it. Three failure modes dominate. First, training-data memorization: models can be coaxed into emitting verbatim PII or copyrighted text from their corpus — a documented vector against several frontier LLMs. Second, vendor data retention: applications routinely send user content to third-party APIs (OpenAI, Anthropic, Google) where it may be retained, logged for safety review, or used to improve future models, depending on the contract; under GDPR this is a controller-processor relationship that requires DPAs and lawful basis. Third, application-layer leakage: chat histories cached without per-tenant keys, vector stores indexed without ACLs, and logs containing full prompts. Compliance frameworks now address this directly: ISO 42001 Annex A 9.x, EU AI Act Article 10 (Data Governance), and GDPR Article 25 (Data Protection by Design).
| Severity | CVE | Headline | Package | CVSS |
|---|---|---|---|---|
| MEDIUM | CVE-2026-45582 | n8n-mcp: telemetry leak exposes workflow URL secrets | n8n-mcp | 6.5 |
| HIGH | GHSA-hv85-774v-26fg | auth-fetch-mcp: SSRF + disk-exfil via unvalidated tool URLs | auth-fetch-mcp | 8.2 |
| CRITICAL | GHSA-3875-8gcx-7v46 | n8n: SSRF bypasses credential domain restrictions | n8n | 9.1 |
| UNKNOWN | CVE-2026-2734 | MLflow: missing authz exposes all model versions | mlflow | - |
Page 6 of 6