Heads-up: collaborator with READ on Secret Scope could delete a key from my shared notebook
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2025 11:42 AM
Hi Databricks team,
Quick heads-up and request for guidance. While collaborating on a notebook in my personal workspace, a colleague who had READ permission on a workspace-backed Secret Scope was able to delete a secret key via terminal/CLI from the shared notebook’s attached cluster.
I’m not sure if this is expected or a misconfiguration, but it felt like a privilege escalation tied to sharing from a personal workspace.
What we saw (brief):
Scope: workspace-backed, colleague explicitly READ only
Context: notebook shared from my personal workspace
Action: databricks secrets delete --scope <scope> --key <key> by the colleague succeeded
Questions:
Is this expected when sharing notebooks from personal workspaces, or is it a known issue?
Any recommended mitigations (e.g., use shared folders, disable cluster terminal, use Key Vault–backed scopes, ensure CLI uses the caller’s identity)?
Happy to share workspace/cluster IDs and timestamps privately if helpful. Thanks!