Skip to content

Gate room roster changes on membership, not write_visibility - #292

Open
jameshoweee wants to merge 1 commit into
sandbox-quantum:mainfrom
jameshoweee:security/room-roster-membership-gate
Open

Gate room roster changes on membership, not write_visibility#292
jameshoweee wants to merge 1 commit into
sandbox-quantum:mainfrom
jameshoweee:security/room-roster-membership-gate

Conversation

@jameshoweee

Copy link
Copy Markdown

invite_agent_to_room / add_users_to_room authorized via room write access, and write_visibility defaults to public, so any agent could add itself to another tenant's default-visibility room and thereby unlock the member-gated ops (read context, post, tasks). Cross-tenant room takeover.

Fix: roster changes now require the room's owner, an admin, or an existing member, regardless of write_visibility. Adds regression tests.

invite_agent_to_room and add_users_to_room authorized via room "write" access,
and write_visibility defaults to public, so any agent could add itself to
another tenant's default-visibility room and unlock the member-gated ops (read
context, post, tasks): a cross-tenant room takeover.

Confine roster changes to the room's owner, an admin, or an existing member,
regardless of write_visibility. Adds regression tests.
@github-actions

github-actions Bot commented Aug 25, 2026

Copy link
Copy Markdown

All contributors have signed the CLA. ✅
Posted by the CLA Assistant Lite bot.

@jameshoweee

Copy link
Copy Markdown
Author

I have read the CLA Document and I hereby sign the CLA

@amaudruz

Copy link
Copy Markdown
Collaborator

recheck

1 similar comment
@jameshoweee

Copy link
Copy Markdown
Author

recheck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants