GPT-5.6 Luna drops 80%, Sol 2.5x faster
AI Gateway passes through upstream price cuts and speed gains with zero markup; existing code gets new rates automatically.
Token economics shift materially for Luna workloads (80% reduction enables new use cases), and Sol's fast mode speed bump directly improves latency-sensitive inference without code changes. Model IDs unchanged means you get the upgrade on next request.
Replace nothing—this is a pure improvement to existing AI Gateway routes. No code changes required. Act now if you're on Luna (lock in 80% savings) or if latency is your bottleneck (Sol fast mode now 2.5x faster). Worth immediate cost re-audit for Luna-heavy deployments.
- “AI Gateway adds no markup on token pricing, so these changes reach you at the upstream rate”
- “GPT-5.6 Luna: 80% price reduction”
- “GPT-5.6 Sol: fast mode now 2.5x faster (up from 1.5x)”
- “Model IDs are unchanged, so existing requests get the new rates and speed with no code change”
pricinglatencygpt-5.6ai-gatewaycost-optimization
Inkling Small ships on AI Gateway with reasoning
Quarter-size model matching Inkling performance, controllable thinking effort, native multimodal reasoning—set model to `thinkingmachines/inkling-small` in AI SDK.
Reduces inference cost and latency for agentic coding and tool-use workflows while maintaining reasoning quality. Zero Data Retention option available per-request, enabling compliance-first deployments without vendor lock-in.
Drops into existing AI SDK calls as a model swap. Requires no setup beyond selecting the model identifier and optionally enabling ZDR flag. Worth trying now for cost-sensitive coding agents and multimodal document workflows; benchmark against your current model first.
- “Inkling Small reaches performance comparable to the larger Inkling model at about a quarter of the size, using much less compute per task”
- “native reasoning over audio and images”
- “Controllable thinking effort lets you trade quality against cost and latency, from minimal to maximum reasoning”
- “set `model` to `thinkingmachines/inkling-small` in the AI SDK”
model-releasecost-efficiencymultimodalreasoningvercel-ai-gateway
Rails Active Storage vips RCE requires immediate patching
Default Rails 7.x/8.x with Active Storage + vips processor exposes arbitrary file read and RCE if your app accepts untrusted image uploads; patch to 7.2.3.2, 8.0.5.1, or 8.1.3.1 immediately, and verify libvips ≥ 8.13.
Active Storage ships enabled by default in production Rails apps. This vulnerability chains image upload handling to code execution without requiring authentication in some scenarios, making it a runtime blocker for any Rails service processing user-uploaded images.
Upgrade Rails to patched versions (7.2.3.2+, 8.0.5.1+, 8.1.3.1+). Separately verify libvips ≥ 8.13; earlier versions cannot disable unsafe operations even after Rails patch. If upgrade blocked, set VIPS_BLOCK_UNTRUSTED=1 or call Vips.block_untrusted(true) as temporary mitigation. WAF is insufficient. Do not delay—PoC reconstruction is likely once diffs go public.
- “Arbitrary file read and remote code execution chain affecting default Rails applications that use Active Storage with the vips image processor”
- “move to Rails 7.2.3.2, 8.0.5.1, or 8.1.3.1 (or later)”
- “the fix depends on libvips itself being version 8.13 or later, earlier libvips builds can't disable the unsafe operations involved at all”
- “Rails 7.0.0 through 7.2.3.1 and 8.0.0 through 8.1.3 don't have that requirement”
- “assumes attackers with AI tooling can reconstruct one quickly once patches ship and diffs go public”
rails-securityactive-storagercevipspatch-urgent
Vercel Sandbox runs isolated agents in single environment
Use createUser() and createGroup() to run multi-agent systems with filesystem isolation and optional shared workspaces in @vercel/sandbox.
Eliminates the operational overhead of spinning up separate containers per agent while maintaining security boundaries. Developers building multi-agent workflows can now coordinate work through shared directories without sacrificing process isolation.
Replaces single-user sandbox patterns and replaces running agents in separate container instances. Requires Vercel Sandbox SDK v1.x with multi-user support; ready to adopt now for new multi-agent projects. Existing single-user code remains compatible.
- “Each agent runs as its own user with a private home directory”
- “users can't read, write, or list each other's files”
- “A group opens a shared workspace when they need to collaborate”
- “Call createUser for each agent; its commands and file operations run as that user”
vercel-sandboxmulti-agentisolationlinux-userscollaboration
Nuxt patches eight vulnerabilities including RCE
Upgrade to Nuxt 4.5.1 or 3.21.10 immediately—high-severity RCE in server islands and authorization bypass in route rules require patched versions, Vercel WAF mitigations are not a replacement.
Server-side RCE and cross-user cache disclosure directly compromise production apps; relying on platform-level protections without upgrading leaves component instantiation, caching, and DoS vectors exposed. Non-negotiable dependency bump for any Nuxt deployment handling authenticated data.
Replace current Nuxt versions with patched releases via `npx nuxt upgrade --dedupe`—requires lockfile refresh and DevTools bump to 3.3.1. Critical for production; no workaround exists. Also required: purge upstream caches if serving authenticated payloads pre-patch. Start now.
- “eight security advisories, including a high-severity server-side remote code execution vulnerability”
- “Nuxt 4: `4.5.1` or later, Nuxt 3: `3.21.10` or later, Nuxt DevTools: `3.3.1` or later”
- “Vercel received advance notice of the server-side remote code execution vulnerability, [GHSA-9473-5f9j-94wq], and deployed platform-wide WAF mitigations before public disclosure”
- “do not rely on them for full protection. Upgrading to a patched version is still required”
- “The newly disclosed authorization bypass is a regression in that earlier fix”
nuxt-securityrce-vulnerabilityserver-islandscritical-upgradecache-disclosure