SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

I Traced CrewAI's Sandbox CVE: 9 Names Missed the Runtime

0
·32 views

A CVE published yesterday afternoon says the Python sandbox in CrewAI, a widely used agent framework, blocked nine module names and still lost. The record's wording is blunt for a CVE: the blocklist "operates at the wrong level of abstraction." The escape it describes never uses an import statement at all. I was researching agent sandbox failures this week anyway. Between the GreyNoise agent swarm report, the SGLang pickle RCE last weekend, and Bengio's agent-misbehavior paper trending on Hacker News, every feed I follow is agent security right now. When my trending scan surfaced CVE-2026-3700

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

xAI's Grok Voice 3.0 Replaces the grok-voice-latest Alias, Upgrading Existing Sessions

xAI launched Grok Voice 3.0 on October 14, and its release notes state that the grok-voice-latest alias now points to this model, so existing sessions using the alias are upgraded automatically. The new speech-to-speech model is priced the same as Grok Voice 2.0 at $0.08 per minute, and xAI has marked version 2.0 as deprecated without giving a retirement date. Artificial Analysis ranks Grok Voice 3.0 first on its Speech to Speech Index with a score of 86.9, ahead of OpenAI's GPT-Live-1 at 83.2. On the agentic τ-Voice benchmark, however, GPT-Live-1 still leads, 74.5% to 71.6%, though Grok Voice 3.0 improved substantially over its predecessor's 56.5%. Developers relying on the alias may see changed behavior since the API endpoint is unchanged but the underlying model is not.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

UTC Cron Patterns Keep Daily Report Emails Timezone-Safe for US and EU SaaS

A developer guide argues that daily report emails fail when a single global schedule ignores recipients' local clocks. It recommends one coarse UTC cron that wakes the application, which then selects users whose local send window matches the current time. Recipients should be stored with IANA timezone identifiers so daylight-saving changes are handled in application code rather than cron syntax. Each send should carry a durable idempotency key derived from the user and local date, so retries do not produce duplicate emails. The article also notes that cron timing has second-level jitter and that exact delivery timing cannot be guaranteed.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

BlazePhoenix Computes DEX Swap Routes On-Chain to Remove Off-Chain Trust

BlazePhoenix is a DEX aggregator on Base, Ethereum, Optimism, Arbitrum and Robinhood Chain that computes trade routes inside the executing transaction rather than on a private server. Unlike typical aggregators, it has no off-chain router that users must trust, since pool state can shift between quote and execution. The contract enforces a minimum-out amount, returns any execution surplus to the user, and sources prices from a Quoter contract that anyone can verify via a plain eth_call. The project is pre-launch, with an independent external audit scheduled before release, and it offers an SDK and an MCP server for AI agents.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

oh-my-agent 20.0.0 replaces deepsec with oma-security and consolidates data under one home

The oh-my-agent CLI shipped five major versions in seven days, from 15.10.0 to 20.0.0, largely through breaking changes that remove old paths rather than adding compatibility layers. The new oma-security tool and /security command replace oma-deepsec and /deepsec with no aliases, routing scans to target-specific engines that require independent validation before findings are confirmed. Global data now lives under a single OMA_HOME directory, defaulting to ~/.oma, with copy-first migration and no runtime fallback to old paths. AgentMemory operations are now scoped to individual projects and profiles, and install and update prepare the default provider unless opted out. Additional changes include user-extensible commit-msg hooks, tooling profiles, fixes to JSON output and scheduling, and a cleaner command surface with generated documentation.

0 comments Read more at DEV Community