Skip to content
NewA calmer, faster ZeroHour
Toolsinfo

Cloudflare’s EmDash 1.0 makes sandboxed plugins ask for access first

Help Net Securityby Mirko Zorz ()2 min read2 · 1 read
AI summary · grok-4.7Summaries by Vani AI

Cloudflare released EmDash 1.0, an open-source CMS that sandboxes plugins until administrators approve access.

Cloudflare released EmDash 1.0, a free open-source CMS that runs each plugin in its own isolated runtime. A plugin starts with only private storage and cannot reach site content, media, users, secrets, the filesystem, or the network until it declares what it needs and an administrator approves it. The plugin registry runs on Bluesky's AT Protocol: publishers sign packages, and EmDash checks the signed commit, checksum, name, version, requested access, and build provenance. There is no central kill switch; moderation can hide a catalog listing but the signed release stays published.

Key facts
  • Each plugin starts with private storage and no content, secret, or network access.
  • Administrators must approve declared capabilities before the runtime grants them.
  • The registry uses AT Protocol, signed releases, and checksum verification.
  • Catalog moderation can hide listings but cannot unpublish a release.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

2 min read at helpnetsecurity.com

Cloudflare released EmDash 1. 0, a free, open source content management system that locks each sandboxed plugin in its own isolated runtime. A plugin starts with access to its own private storage.

Help Net Security

By Mirko Zorz · helpnetsecurity.com

Read the full article at Help Net Security

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.