DeepSeek Harness RCE vulnerability (CVSS 9.8): what's known and how to check your install

The hottest new agent framework just got its first critical security flaw. An unauthenticated remote code execution (RCE) vulnerability in DeepSeek Harness was disclosed this week, rated CVSS 9.8 — the top of the severity scale — and a proof-of-concept is already public. If you installed DSH during the recent hype wave, this one is worth five minutes of your attention.

What we know

• The flaw: unauthenticated remote code execution — an attacker who can reach a running Harness instance can run code on the host.
• Severity: CVSS 9.8 (Critical).
• Tracker: disclosed by Chinese security vendor QiAnXin (奇安信) under QVD-2026-52644.
• Status: a public proof-of-concept is circulating, which raises the urgency from "theoretical" to "actively exploitable."

Who's affected

Anyone running DeepSeek Harness (dsh), especially in a configuration where the web UI or its ports are reachable beyond localhost. If you only ever ran dsh web locally and never exposed it, your exposure is much lower — but "much lower" isn't "zero," so check anyway.

What to do, in order

1. Pin your version. Check what you're running (dsh --version) and whether a patched release has landed for your install channel.
2. Update to the patched version. The fix typically ships in a new release — don't sit on the vulnerable one.
3. Don't expose DSH to the internet. Until you're on a patched build, keep the web UI bound to localhost, behind a firewall, or off public networks.
4. Watch the official channel. Follow the GitHub releases and security advisories for the definitive patch note, rather than third-party summaries.

The bigger picture

This is the predictable cost of explosive growth: a framework that went from zero to 150K stars in a fortnight was always going to attract security researchers — that's a sign of relevance, not failure. But relevance is not maturity. The lesson for teams is the same one we've been repeating: "it works, but you have to watch it" now applies to security, not just features.

For DSH specifically, the fix cadence has been weekly, so a patched release is likely fast. The real test is whether the project treats this as a one-off or as the start of a real security process.