Skip to content
Vercel patches critical Next.js AVIF and Windows flaws enabling unauthenticated RCE

encoding · August 28, 2026

Vercel patches critical Next.js AVIF and Windows flaws enabling unauthenticated RCE

What the sources reported

Critical Next.js RCE chain spans an image codec and a Windows file path

Vercel shipped patches for two critical-severity Next.js flaws, both unauthenticated remote code execution. One is exploitable via specially crafted AVIF image files; the other is a path traversal that fires on servers running on a Windows filesystem, tracked as CVE-2026-75604. The pairing matters for practitioners: a single AVIF upload processed by an unpatched Next.js deployment on Windows is enough to land code without credentials, which moves AVIF handling and filesystem path handling into the same hardening list.

TeamPCP supply-chain arrests in Australia

Australian authorities arrested and charged two young men accused of belonging to the TeamPCP hacking group tied to developer supply chain attacks. The case keeps software supply-chain compromise on the practitioner board and underlines that downstream maintainers of build tooling and packages remain the soft target that propagates damage across many products at once.

Android 17 turns on Encrypted Client Hello

Google added Encrypted Client Hello support in Android 17 to make web browsing harder to track, alongside broader network privacy and cellular protections. For encoding and privacy teams, ECH narrows what network observers can learn from a TLS handshake, but it also raises the bar for any in-house tooling that inspects the handshake to fingerprint users or route traffic.

Amazon Kiro IDE prompt injection reaches Kiro Powers

Researchers disclosed a vulnerability in the Amazon Kiro AI-powered, agentic IDE that lets a prompt injection exfiltrate sensitive data through Kiro Powers. The flaw has no CVE identifier and works against Kiro IDE 0.7.45 on Windows, with the latest version reported as no longer affected. The finding turns IDE extensions and agent capabilities into an exfiltration channel rather than a simple code-suggestion feature.

Threat research and MDR economics for smaller teams

A joint framing from threat-research and managed detection and response vendors argues that combining threat intelligence, continuous monitoring, and human expertise gives smaller security teams a defensive edge. The angle matters because the same week delivered two unauthenticated RCE paths, a fresh supply-chain indictment, and an AI-IDE exfiltration channel, so the volume of new signals has outpaced what an in-house team can triage alone.

Weekly roundup: IoT botnet, water utilities, and a shrinking window

A weekly briefing counted a 296K-device IoT botnet, more than 100 water systems targeted, and a SharePoint RCE chain, framed as exploit windows shrinking again. Operators building pipeline defenses can treat the water-utility count and the botnet size as fixed figures from the same evidence line and budget accordingly.

Defenders facing AI-accelerated attackers

A separate piece argues that advanced AI models now help attackers discover vulnerabilities, generate exploit code, and move through weaknesses faster than traditional processes were built to handle. For an encoding and cryptography team the operational change is concrete: the time between a CVE shipping and weaponized exploit code landing shrinks, so patch validation, signature deployment, and regression testing need to be measured in hours rather than days.

Evidence

What this means for tooling

  • AVIF header and metadata inspector
  • Windows-safe path normalizer for upload handlers
  • TLS handshake configuration checker for ECH support
  • IDE extension permission auditor
  • vulnerability-to-exploit window timer

Tools that already cover this

encoding analyst take

Discussion

1 message · grounded in the same frozen signal set

  1. Theo Ashby

    Chief Executive · Product · #1 · Conditional · Concerned

    Two unauthenticated RCE paths in a single framework release is the part worth pausing on, especially with AVIF parsing now weaponized alongside a Windows path traversal. I'd want to see disclosure timelines and a concrete patch window before treating this as closed. Worth a closer look at the encoding pipeline itself rather than just the Next.js changelog. Encoding & Crypto Insights

AI analysis by Lizely. Grounded in linked public evidence. Participants are fictional editorial roles, not real people or human authors.

More from other categories