Skip to main content
← All research

The Localhost Exposure Report 2026

Exploited dev and AI tools, tunnel abuse on record, tunnel hostnames in public certificate logs, and free-tier changes: the risks of sharing apps from a laptop.

Updated October 1, 2026. Licensed CC BY 4.0.

Key findings

19developer, AI, and self-hosted tool entries added to CISA KEV in 2026, against 5 in 2025
11published reports of criminals using localhost tunnels, 9 naming Cloudflare and 6 naming ngrok
18 of 22tunnel tools give a shared app a public URL by default
7tunnel tools now put a warning or reminder page in front of visitors

1. The tools developers share are being exploited

Of the 38 CISA Known Exploited Vulnerabilities entries for the developer, AI, and self-hosted tools we track, 19 were added in 2026 alone. AI and ML tools such as Langflow, LiteLLM, n8n, Ray, and MLflow account for 11 of those, against 1 in 2025. CISA’s Vite entry applies only to dev servers exposed to the network, and a public tunnel URL also puts a dev server on the internet. Two caveats: we track tools that already have catalog entries, and most of these AI tools are only a few years old, so the jump partly reflects what we chose to track and when the tools appeared. The 2026 count covers the year so far.

  • 20212
  • 20227
  • 20231
  • 20244
  • 20255
  • 202619

Data: Developer and AI tools in CISA KEV

2. Tunnels are routine attacker infrastructure

Security vendors, governments, and tunnel providers have documented tunnel abuse since at least 2021. Proofpoint tracked campaigns that used account-less TryCloudflare tunnels to deliver remote access trojans; the joint #StopRansomware advisory on Akira lists ngrok among its operators’ tools; and Microsoft’s September 2026 report describes a ransomware affiliate using both cloudflared and ngrok.

Data: Localhost tunnel abuse ledger

3. Tunnel hostnames can be found

Certificate Transparency logs are public, and a peer-reviewed study measured first requests arriving on average 5.9 minutes after a certificate was registered. Tailscale’s documentation warns that machine names are published in those logs when HTTPS is enabled, which Funnel requires. By contrast, the qurl.site hosts that qURL™ recipients land on are covered by a wildcard certificate: on October 1, 2026 the logs showed 3 qurl.site names in total, so no app or link gets its own entry.

Sources: Kondracki et al., USENIX Security 2022, Tailscale Funnel, Tailscale: Enabling HTTPS

4. Free tiers and abuse controls

10 of the 22 tunnel tools we compared require an account before the first URL, and 7 show visitors a warning or reminder page. Changes we track:

  • zrok v2.0.9 is released; the CLI is zrok2, and private shares are closed to everyone but the accounts you grant unless you pass --open. source
  • Cloudflare announces protected Quick Tunnels: --allowed-mail sends listed visitors an emailed one-time PIN, with no Cloudflare account on either side, for sessions of up to four hours. source
  • Cloudflare's quick tunnel documentation adds --allowed-mail, an optional email one-time PIN in front of a quick tunnel. source
  • ngrok requires card verification before free accounts can open TCP endpoints, citing reports of its agent being bundled into malware. source
  • ngrok describes the anti-phishing measures applied to free accounts, including the browser warning page. source

Data: Every way to share localhost, compared

What to do when you share an app

  • Keep dev servers and model servers bound to localhost; avoid --host and 0.0.0.0.
  • Prefer access that ends on its own. Of the tools compared, only qURL documents single-use links that expire. A link opens one session for the browser that opened it; another browser on the same public IP cannot use its access.
  • Keep your app’s own login for anything sensitive, whatever carries the traffic.
  • If your developers don’t need them, consider blocking free tunnel domains on your network, as SpearTip recommends for trycloudflare.com.

For a shorter explanation of the risk and sharing choices, read Is exposing localhost safe?

Method

This report draws on the datasets and sources linked above. Each dataset publishes its sources, the date it was built, and how to rebuild it. The Certificate Transparency finding cites published research and Tailscale’s documentation; the only names we counted are qurl.site’s own.

Frequently Asked Questions

Is it safe to share a dev server with a tunnel?

Dev servers are not built for hostile traffic. 19 entries for developer, AI, and self-hosted tools were added to CISA’s Known Exploited Vulnerabilities catalog in 2026 so far, and 18 of the 22 tunnel tools we compared give the app a public URL by default.

Do attackers really use localhost tunnels?

Yes. We verified 11 published reports; 9 involve Cloudflare tunnels and 6 involve ngrok, for malware delivery, phishing, remote access, and data theft. The most recent is from Microsoft Threat Intelligence (2026-09-24).

Cite this

LayerV (2026). The Localhost Exposure Report 2026. https://layerv.ai/research/localhost-exposure-2026 (updated 2026-10-01). CC BY 4.0.

Book a pilot

Tell us what to hide. We’ll scope a pilot.

Enterprise starts with a paid pilot on one application, typically 60 to 90 days, credited in full toward year one if you convert within 60 days. After that, an annual package sized to what you protect, not per seat.