🦋 New version release#307
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@smooai/smooth-operator@1.36.2
Patch Changes
bd7fb5b: SECURITY (Rust server): owner-check every sessionId-taking WebSocket action.
The per-user scoping added for the read paths left the write paths loading a
session by raw client-supplied id.
send_messagewas the worst case: anauthenticated user who knew or guessed another user's
sessionIdcould send amessage into that session — the turn replayed the victim's conversation history
as context and streamed the agent's reply back to the sender, so the write
hole was also a read of the victim's conversation.
get_session,verify_otp,confirm_tool_action,submit_interactionandrename_conversationhad thesame gap.
All of them now route through a single
scoped_sessionchokepoint (mirroringthe Go dispatcher's
scopedSession): it loads the session and hides it unlessthe connection's authenticated principal owns its conversation, returning
exactly what an unknown id returns — so "not yours" is byte-identical to "never
existed" and cannot be used as an existence oracle. A storage error is a denial.
Unauthenticated single-user deployments (the
thdaemon /LocalServerembedding) stay unscoped, and org scoping remains as defense in depth.
@smooai/smooth-operator-web-chat-example@0.0.38
Patch Changes