The Intake — Sunday, October 18, 2026

On the substrate

Langflow's MCP stdio transport carries an actively exploited RCE

The Hacker News CVE-2026-105740 Previdian

If you've been running Langflow to orchestrate multi-step agent workflows and have left MCP server command configuration accessible to authenticated users, this week's advisory names the risk. Langflow versions prior to 1.9.0 pass the MCP stdio transport's command configuration field directly to bash -c. No validation, no allowlisting, and no sandboxing is applied. Any authenticated user can achieve full remote code execution through this path.

Previdian logged 1,706 exploitation attempts through October 17. The traffic came from 27 unique IP addresses. Attack volume ramped sharply starting October 11. Documented paths include crafted HTTP POST requests to the MCP server configuration endpoint. Separately, LD_PRELOAD injection via environment variable override is also documented. The flaw is tracked as CVE-2026-105740, rated at CVSS 9.9.

Version 1.9.0 patches CVE-2026-105740. A companion issue, CVE-2026-105697, is patched in version 1.10.3. If you're running Langflow before 1.9.0 and your deployment accepts user-supplied MCP server command configuration, the configuration endpoint is the active attack surface.

---

Meta releases Muse Spark Open 816B, an open-weight model built for agentic workloads

Hugging Face model card Unite.AI 9to5Mac

If you've been tracking open-weight models for agentic coding and tool-use workflows, Meta's October 15 release adds an 816B-parameter option to that class. The model explicitly targets agentic workloads. Muse Spark Open is released under the Muse Model License. Its mixture-of-experts architecture uses 256 experts. Top-8 routing activates 42B parameters per forward pass.

The model supports a 1M-token context window. A 1.8B-parameter perception encoder handles text, image, video, and audio input. Meta's model card reports SWE-Bench at 60. GPQA Diamond scores at 89.0. MCP-Atlas, an agentic benchmark included in the card, scores at 89.2. Meta's primary design targets include agentic task completion and coding agent workflows. Multi-step tool invocation with error recovery is also in scope.

Local deployment requires 700GB VRAM at NVFP4 quantization. An alternative path runs via MLX on an M5 Ultra Mac Studio. If you're evaluating open-weight options for agent workloads and your infrastructure runs on Apple Silicon, the MLX path via M5 Ultra is the deployment route documented in the model card.

---

Claude Code v2.1.302 ships an official plugin system and a 3x first-token latency improvement

Releasebot (Anthropic October 2026) CryptoBriefing Tech Insider

If you've been treating Claude Code startup latency as a fixed cost in your development workflow, v2.1.302 changes that number. Per Anthropic's release notes, first-token latency has dropped from 4.07 seconds to 1.33 seconds. The improvement accumulated since August 2026. v2.1.301, released October 16, reduced filesystem calls for plugin command and agent file loading. The improvement is most pronounced on Windows.

Version 2.1.302 shipped October 17. It adds client-side auto mode model selection via the CLAUDE_CODE_AUTO_MODE_MODEL environment variable. Idle compaction configuration controls are also new in this release. The plugin system adds a prompt.change hook for tracking prompt modifications. MCP server compatibility updates to protocol version 2026-07-28. The October 15–17 window delivered three consecutive releases.

If you're building Claude Code plugins, prompt.change is now an official hook for observing and intercepting prompt modifications. If you've been experiencing higher startup latency on Windows specifically, v2.1.301's filesystem call reduction is the change that addresses it.

---

For operators

Character.AI files Chapter 11; 12 million users' conversation histories enter a bankruptcy sale process

TechCrunch NBC News Deadline

If you're building an AI product that stores user conversation data, Character.AI's Chapter 11 filing is a concrete example of what that data looks like in an insolvency proceeding. Character.AI filed October 13. The company reported monthly losses of $8–9 million. Monthly active users at filing totaled 20 million. Assets and liabilities at filing were listed between $50 and $100 million.

Disney is the stalking-horse bidder at $20 million for assets. The bid includes a non-exclusive perpetual technology license. Karandeep Anand is Disney's CTO, having joined in September 2026 from Character.AI, where he had served as CEO. The sale places 12 million users' conversation histories in scope for transfer to the acquiring entity. The expected close: late November–early December 2026.

Character.AI had previously settled lawsuits related to chatbot interactions with minors and banned minors from the platform before filing. If you're storing user conversation histories in your own product, the Character.AI filing documents how that data enters a sale process: 12 million conversation records, transferable to the acquiring entity as part of the asset package.

---

Microsoft Agent Framework Python 1.22.0 breaks persisted-state compatibility for rolling deployments

GitHub releases (microsoft/agent-framework) AI Agent News Developer Digest

If you're running rolling deployments with the Microsoft Agent Framework Python SDK, version 1.22.0 introduces a state-store compatibility break. Any version boundary in your deployment will surface it. Pre-1.22.0 runtimes cannot read records containing hosted or merge_mode fields. Running mixed-version workers against the same state store without isolation will produce incompatibility failures.

Python 1.22.0 released October 15. New additions include Python 3.15 support for the core package and a Cosmos memory provider. OAuth consent now surfaces in non-streaming Foundry responses. Breaking changes include consolidated content identity and stricter AG-UI request trust checks. HTTP response body limits in the declarative package are now configurable — also a breaking change. The prior Python release was 1.21.0 on October 8.

If you're mid-rollout with a version boundary inside your deployment, reads on records written by newer workers will fail. The cutover must complete, or the state store must be isolated per-version, before reads succeed.

---