Evidence record / cursor
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-10-13-cursor-cloud-wildcard-network-entries-now-include-the-parent-domain
Cloud wildcard network entries now include the parent domain. A Cloud Agents allowlist entry for a wildcard subdomain now includes the apex domain too. Existing wildcard entries can therefore authorize a destination outside their earlier meaning.
Channel: docs-only (Cloud Agents hosted policy notes). Half: both. Date: week of 2026-09-28.
Operator consequence: Audit cloud wildcard entries whose parent domain hosts a different service or trust level. Replace a wildcard with explicit destinations when the broader reach is unwanted. Evaluate cloud egress separately from the local sandbox policy.
Receipt
Finding metadata
Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0
Finding ID: 2026-10-13-cursor-cloud-wildcard-network-entries-now-include-the-parent-domain
Profile citations
- cursor / claim / cloud-wildcard-parent-domain
Source links
Primary links, including exact changelog lines when available.
- official docs2026-10-13-cursor-cloud-wildcard-network-entries-now-include-the-parent-domainweb.archive.org/web/20261007020951/https://cursor.com/docs/release-notesofficial docs2026-10-13-cursor-cloud-wildcard-network-entries-now-include-the-parent-domaincursor.com/docs/release-notes/cloud-agents#sep-28-2026
Versioned source: run artifact