OpenClaw Security Risks: What New Zealanders Need to Know

Published March 2026 · 7 min read

OpenClaw has gone viral in 2026 — 163,000 GitHub stars, a Wikipedia article, and coverage from Immersive Labs to the Institutional Investor. But alongside the hype, a clear narrative has emerged from cybersecurity researchers: OpenClaw has real security risks, and most people installing it have no idea what they're doing.

As New Zealand's dedicated OpenClaw installation service, we've read every security advisory. Here's an honest breakdown of what the risks actually are — and what it takes to eliminate them.

What the Security Researchers Found

In early 2026, Immersive Labs published a detailed security review of OpenClaw that made waves in the security community. Their findings:

• 6 CVEs in early 2026, including two command injection vulnerabilities patched within days of each other
• 42,000+ exposed instances found globally with the gateway port open to the internet
• 824+ malicious skills identified on ClawHub, the community skill marketplace
• Prompt injection risks where crafted input can cause unintended agent actions

A comprehensive r/selfhosted thread documenting every incident went viral, with 149 upvotes and detailed commentary from sysadmins who'd actually audited running instances.

The Real Risk: It's Not the Software — It's the Setup

Here's what the headlines miss: every major security incident with OpenClaw came down to misconfiguration, not fundamental flaws in the software itself.

The three most common mistakes:

What a Secure OpenClaw Installation Looks Like

A properly secured OpenClaw setup includes:

• ✅ Gateway bound to localhost only — not accessible from outside the machine
• ✅ UFW firewall enabled with deny-all inbound, only SSH/80/443 open
• ✅ Tailscale for secure remote access (no open ports, encrypted tunnel)
• ✅ SSH key-only authentication, root login disabled
• ✅ OpenClaw kept up to date (patch CVEs as they're released)
• ✅ Only verified, high-reputation skills installed
• ✅ API keys stored in secrets manager, not hardcoded in config
• ✅ Daily security audit cron job monitoring for anomalies

This isn't complicated — but it requires knowing what you're doing. The 42,000 exposed instances weren't the result of malicious actors exploiting sophisticated vulnerabilities. They were people who followed a basic install tutorial without understanding the security implications.

For New Zealand Businesses: The Privacy Angle

Under New Zealand's Privacy Act 2020, businesses have obligations around how personal information is stored and processed. An exposed OpenClaw instance that has access to emails, calendars, and documents is a potential Privacy Act breach waiting to happen.

This is why we recommend OpenClaw on dedicated hardware at your premises — not cloud VPS — for any business handling client data. Your data stays on your hardware, in your building, under your control.

The Bottom Line

OpenClaw is genuinely powerful technology — and yes, it has had security issues. But every one of those issues is solvable with proper configuration. The question isn't whether OpenClaw is safe. It's whether your OpenClaw installation is safe.