Next.js Patches Two Critical RCE Vulnerabilities in Versions 15.5.24 and 16.3.3
Next.js has received a security update to fix two critical vulnerabilities that can lead to remote code execution without authentication. The patches were made available in versions 15.5.24 and 16.3.3.
The first flaw, CVE-2026-75604, received a CVSS score of 9.0 and affects applications hosted on Windows servers that use Pages Router or App Router without Cache Components. The issue is related to path traversal. An attacker can manipulate paths processed by the application and, under specific conditions, achieve code execution on the server without requiring credentials or user interaction. Vulnerable versions include those from 13.4 up to but not including 15.5.24, as well as the 16.0 line up to but not including 16.3.3. There is no workaround for affected Windows servers.
The second vulnerability targets the Image Optimization API when AVIF files are processed. A specially crafted malicious AVIF file can exploit the image processing pipeline and result in code execution. This flaw affects versions from 10.0.0 up to releases prior to 15.5.24, plus versions 16 prior to 16.3.3.
Administrators should update dependencies, rebuild containers, and confirm that production environments run Next.js 15.5.24 or 16.3.3 or later, with priority given to Windows servers and applications that process user-submitted images.
Related articles
GitSpawn Exposes Persistent Git Config Execution Risks in Coding Agents
Manifold Security released GitSpawn, detailing eight vulnerabilities across seven coding agents where opening a folder triggers arbitrary code execution via Git configuration before any user prompt. The core issue stems from the core.fsmonitor setting in .git/config, which Git executes during index updates like git status or git diff. While vendors including Anthropic patched Claude Code in version 2.1.196, the fix only blocks agent-initiated calls and leaves manual Git commands or other tools vulnerable. Additional vectors include nested bare repositories tracked under CVE-2026-45033 affecting GitHub Copilot CLI and unpatched agents such as Qwen Code and Grok Build. The researcher also released the Stroq tool to inspect repositories for dangerous settings like core.fsmonitor and postinstall scripts before opening them. The findings highlight that repository trust mechanisms from 2021 remain bypassed by modern AI coding tools.
Critical Unauthenticated File Upload Flaw in WooCommerce Wholesale Lead Capture Enables Active PHP Web Shell Attacks
A critical vulnerability tracked as CVE-2026-27540 affects WooCommerce Wholesale Lead Capture versions 2.0.3.1 and earlier, allowing unauthenticated attackers to upload arbitrary files including PHP web shells. The flaw resides in the wwlc_file_upload_handler AJAX action, where the file extension allowlist can be manipulated through the file_settings parameter to accept .php files. Exploitation has been observed in the wild with more than 100,000 blocked attempts since June 2026, including sustained campaigns from repeat IP addresses. The developer released version 2.0.3.2 on 20 February 2026 to address the issue, yet many sites remain unpatched. Organizations are advised to update immediately, audit wp-content/uploads for unexpected PHP files, and monitor admin-ajax.php requests for suspicious activity. In confirmed compromise cases, full remediation requires credential rotation and restoration from verified backups.
AWS Systems Manager Agent Flaw Allows Bypass of Port Forwarding Restrictions
Amazon has fixed a vulnerability in the AWS Systems Manager agent that permits an authenticated attacker to bypass restrictions on port forwarding sessions. The issue, tracked as CVE-2026-89049, stems from inadequate validation of equivalent representations of blocked link-local addresses. As a result, attackers can reach the EC2 instance metadata service at 169.254.169.254 and obtain temporary credentials tied to the instance's IAM role. Affected versions are those prior to 3.3.4851.0, with the fix included in that release and all subsequent versions. AWS recommends reviewing custom builds of the agent, restricting access to the AWS-StartPortForwardingSessionToRemoteHost document, auditing Session Manager activity, and applying least-privilege principles to IAM roles.
Vulnerability Management in Atypical Environments: ICS, Networks, IoT, Mobile, Hardware, and ML Systems
Vulnerability management follows the same core process across environments—identify assets, scan, assess risk, prioritize, remediate, and verify—but each domain introduces critical constraints. In industrial control systems, scanning must avoid disrupting physical processes, requiring audit-mode authenticated scans, digital twins for testing, and strict change windows. Network devices frequently suffer from poor segmentation, default SNMP community strings, and exposed management interfaces that enable traffic redirection or configuration tampering. IoT ecosystems remain plagued by default credentials, as demonstrated by the Mirai botnet that took down major DNS infrastructure in 2016, while modern botnets like Reaper and VPNFilter exploit unpatched firmware at massive scale. Machine learning systems face novel threats including prompt injection, prompt leaking, and jailbreaking that can bypass safety controls or exfiltrate training data. Mobile platforms suffer from extreme fragmentation that prevents timely patching of vulnerabilities such as Stagefright, Pegasus, and BlueBorne. Hardware-level flaws like Spectre, Meltdown, and BadUSB demonstrate that even firmware and silicon require coordinated microcode, OS, and application updates.