This release includes 1 security fix for security teams reviewing exposed deployments.
Affected surfaces
Summary
AI summaryReject unsafe chatSessionId values at /connect to prevent path traversal attacks.
Full changelog
Highlights
-
Reject unsafe `chatSessionId` at `/connect` (#1905, follow-up to #1895) — the `/connect` route now validates `chatSessionId` at entry (400 on hostile format) and `connectSession` refuses to persist an unsafe value even if a caller bypasses the route. Without this gate, a POST with `{"chatSessionId": "../../etc/x"}` would land in the state file and a later `/history` command would read that hostile value back into a filesystem reader with no traversal guard.
-
New export: `isSafeSessionId(sessionId)` from `./chat-state` — safe char class `[\w.-]{1,200}` plus explicit `..` rejection. Accepts every legit session-id form (UUIDs, transport-chat-timestamp triples, 16-hex shorts, dotted legacy names).
Security Fixes
- Prevent path traversal by rejecting unsafe `chatSessionId` values at `/connect` and in persisted session data (CVE not specified)
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About MulmoClaude
All releases →Related context
Related tools
Beta — feedback welcome: [email protected]