TypeBot Bug, Next.js Patch, Axios Supply-Chain Risk

Four things happened today that matter if you shipped an app with an AI builder. One is a real vulnerability with a CVE number. One is a platform-level patch you may or may not have gotten automatically. One is a supply-chain attack on a package half the internet depends on. And one is a Reddit post that shows exactly how secrets end up scattered across a vibe-coded stack.

TL;DR

• CVE-2026-62861: TypeBot fixed a bug where any workspace member could disable another workspace's custom domain, because the delete handler trusted a client-supplied workspace ID instead of verifying it server-side.
• Next.js shipped a critical security release in August 2026, including an unauthenticated RCE in Image Optimization. Vercel-hosted apps are patched automatically. Self-hosted apps are not.
• The axios npm package was hijacked in a supply-chain attack discovered March 31, 2026. Make sure you're on axios@1.14.0 or later.
• A vibe-coder on r/vibecoding asked Claude to clean up docs and ended up realizing their secrets were sitting in plaintext across env files and config — a common, not rare, pattern.

A chatbot builder's authorization bug: trust the server, not the client

TypeBot, a chatbot-building tool, patched CVE-2026-62861 in version 3.18.0. The bug: the custom-domain delete handler checked a caller's permissions against a workspace ID the client sent in the request, then removed the domain from a shared Vercel project before confirming that domain actually belonged to that workspace. Any authenticated, non-guest member of any workspace could knock another workspace's bots offline.

This isn't a data leak. It's a broken tenant-isolation check. But the underlying mistake is one AI coding assistants make constantly: authorizing an action using an ID the client supplied, instead of looking up the real owner on the server before acting. If your app has any multi-tenant logic — teams, workspaces, organizations — this is exactly the class of bug worth checking for, regardless of which builder you used.

Next.js patched a critical bug — are you self-hosted?

Next.js disclosed two vulnerabilities in its August 2026 security release. One, GHSA-2xp9-vwfh-vxw4, lives in the upstream libheif dependency and can lead to unauthenticated remote code execution when Image Optimization processes a crafted AVIF file.

If your app runs on Vercel, you're already protected — no action needed. If you self-host Next.js, or run it on another platform, you need to update yourself. Many apps built through AI coding tools default to Next.js under the hood. Check where yours actually deploys before assuming someone else patched it for you.

Your dependencies can turn against you: the axios supply-chain attack

The axios npm package — a dependency in an enormous share of JavaScript projects, including ones AI assistants pull in without asking — was compromised in an active supply-chain attack discovered March 31, 2026. Malicious versions were published, then removed from the npm registry. The safe release is axios@1.14.0.

Vercel confirmed no Vercel systems were affected and blocked build-infrastructure traffic to the attacker's command-and-control host. If your project pulls axios — directly or through another package — confirm you're locked to a safe version. AI builders add dependencies fast and rarely warn you when one of them gets compromised after the fact.

Secrets sprawl is the default, not the exception

On r/vibecoding, someone asked Claude to tidy up their home-lab documentation and discovered they had admin and database passwords sitting in plaintext across env files — so Claude built them a full key-management app to move everything into Azure Key Vault. That's a funny story about a homelab. It's also a completely normal outcome of vibe coding a real product: secrets get typed into .env files, copied into config, hardcoded into a