# DeepSeek leaves ClickHouse database open: chat logs and API keys exposed · pwn.watch

> Wiz found two DeepSeek ClickHouse instances open to the internet without authentication. Its query interface allowed arbitrary SQL and exposed a log_stream table with over a million entries, including plaintext chat history, API keys and backend details. DeepSeek locked it down within an hour of being told.

Page: https://pwn.watch/i/deepseek-exposed-clickhouse-database-january-2025 · generated 2026-10-22T22:00:08.805Z

## Status
- Severity: high · status: closed · patch: patched
- Product: DeepSeek backend (ClickHouse)
- Started: 2025-01-29 · closed: 2025-01-29
- Affected: n/a
- Fixed in: Database secured by DeepSeek

## Follow this incident
- RSS (one item per update): https://pwn.watch/i/deepseek-exposed-clickhouse-database-january-2025/feed.xml
- JSON Feed: https://pwn.watch/i/deepseek-exposed-clickhouse-database-january-2025/feed.json
- Full data (timeline, sources, posts, agentBrief): https://pwn.watch/i/deepseek-exposed-clickhouse-database-january-2025.json
- This file: https://pwn.watch/i/deepseek-exposed-clickhouse-database-january-2025/llms.txt

## Updates (newest first)
- 2025-01-29: Wiz finds the exposed database and reports it; DeepSeek secures it within an hour (https://www.wiz.io/blog/wiz-research-uncovers-exposed-deepseek-database-leak)

## Fix brief
# Security brief: DeepSeek leaves ClickHouse database open: chat logs and API keys exposed

Source: https://pwn.watch/i/deepseek-exposed-clickhouse-database-january-2025 · status: closed (closed Jan 29, 2025) · severity: high · updated Jan 29, 2025

## Patch status
**PATCHED: fixed releases exist. Upgrade to a fixed version.**

## What it is
Wiz found two DeepSeek ClickHouse instances open to the internet without authentication. Its query interface allowed arbitrary SQL and exposed a log_stream table with over a million entries, including plaintext chat history, API keys and backend details. DeepSeek locked it down within an hour of being told.

Severity detail: Unauthenticated database exposure; chat logs and secrets

- Product: DeepSeek backend (ClickHouse)

## Affected versions
- n/a

## Check whether you're affected
No generic command applies (the product is a hosted service, appliance or desktop app). Check the installed version in its admin UI / About screen and compare with the versions above.

## Fix
Upgrade to one of these fixed versions (or later on the same branch):
- Database secured by DeepSeek

After upgrading, re-run the checks above and redeploy/restart the affected services.

## Secrets to rotate
This incident involves possible credential exposure. Rotate any credentials (API keys, tokens, env vars, SSH keys) that were present on affected systems or in affected builds while vulnerable/compromised versions were installed, and review access logs.

## Latest updates
- Jan 29, 2025: Wiz finds the exposed database and reports it; DeepSeek secures it within an hour

## Write-ups & news
- [Wiz Research Uncovers Exposed DeepSeek Database Leaking Sensitive Information](https://www.wiz.io/blog/wiz-research-uncovers-exposed-deepseek-database-leak)
- [Sensitive DeepSeek data exposed to web, cyber firm says](https://www.reuters.com/technology/artificial-intelligence/sensitive-deepseek-data-exposed-web-israeli-cyber-firm-says-2025-01-29/)
- [DeepSeek exposes database with over 1 million chat records](https://www.bleepingcomputer.com/news/security/deepseek-exposes-database-with-over-1-million-chat-records/)
- [Exposed DeepSeek Database Revealed Chat Prompts and Internal Data](https://www.wired.com/story/exposed-deepseek-database-revealed-chat-prompts-and-internal-data/)

---
Machine-readable: https://pwn.watch/i/deepseek-exposed-clickhouse-database-january-2025.json · all incidents: https://pwn.watch/incidents.json. Verify against the vendor advisory before changing production systems.