# wasmCloud 2.11: Policy that enforces, backends the operator owns, and a host that bounds itself

DevFeed: [wasmCloud 2.11: Policy that enforces, backends the operator owns, and a host that bounds itself](<https://devfeed.tech/articles/wasmcloud-2-11-policy-that-enforces-backends-the-operator-owns-and-a-host-that-bounds-itself-93087.md>)

Original publisher: [Read original article](<https://wasmcloud.com/blog/wasmcloud-2-11-release/>)

Author: Eric Gregory

Published: 2026-10-21T00:00:00Z

Content type: release

Language: en

Sources: [wasmCloud](<https://devfeed.tech/sources/wasmcloud-blog.md>)

Topics: [wasmCloud](<https://devfeed.tech/topics/wasmcloud.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [backends](<https://devfeed.tech/tags/backends.md>), [components](<https://devfeed.tech/tags/components.md>), [control](<https://devfeed.tech/tags/control.md>), [egress](<https://devfeed.tech/tags/egress.md>), [memory](<https://devfeed.tech/tags/memory.md>), [operator](<https://devfeed.tech/tags/operator.md>), [policy](<https://devfeed.tech/tags/policy.md>), [process](<https://devfeed.tech/tags/process.md>), [raw](<https://devfeed.tech/tags/raw.md>), [resource](<https://devfeed.tech/tags/resource.md>), [socket](<https://devfeed.tech/tags/socket.md>), [volumes](<https://devfeed.tech/tags/volumes.md>), [wasmcloud](<https://devfeed.tech/tags/wasmcloud.md>)

## AI overview

wasmCloud 2.11.0 makes raw-socket egress and guest-memory policies enforce by default, and moves multiplexed plugin backend addresses under operator control. Workloads that previously set backend URLs, roots, or prefixes may fail under the default deny policy; the release recommends setting `workloadConfig: warn` first to identify affected manifests. `hostPath` mounts also require an explicit host allowlist, which is a host-wide guardrail rather than workload isolation. The host now refuses guest growth and new starts above its process-memory threshold, though this sampled admission control cannot stop in-flight allocations or plugin buffers; the container limit remains the actual boundary. `allowedHosts` grants matching DNS lookups, but raw-socket hostname access still needs a name grant, and `allowedHosts: ["*"]` grants no lookup. The release also fixes sibling-component resource-handle failures and updates Wasmtime to 48.0.7, addressing a critical aarch64 miscompile and other listed advisories. Upgrade checks include the changed OCI cache, memory sizing, and restrictive NATS permissions.

## Source excerpt

wasmCloud 2.11 turns raw-socket egress and guest memory enforcement on by default, moves multiplexed backend addresses under operator control, gates hostPath volumes, bounds the host process footprint, and fixes resource handles passed between sibling components.