Skip to content
What are you looking for?. Open searchSR

Tags

dependencies

14 items
NEXT.JS7vulnerabilities patched, two still pending
Toolsstrong signal

Next.js 16.3.8 and 15.5.27 fix seven vulnerabilities, led by an SSRF in image optimization

Next.js published its September security release on September 30, 2026. Versions 16.3.8 and 15.5.27 close one high, five medium, and one low severity vulnerability, from server-side request forgery in image optimization to cache poisoning on self-hosted sites. Two more fixes, one critical and one high, are held for a later release while an upstream dependency catches up. If you self-host, most of the list applies to you.

Next.js Blogverified

NEXT.JS16.3.7nine security fixes, scheduled for September 3
Toolsmedium signal

Next.js schedules a September 30 security release that fixes nine vulnerabilities

The Next.js team announced on September 23, 2026 that versions 16.3.7 and 15.5.27 will ship on September 30, 2026. The release addresses nine vulnerabilities, one of them rated critical. The advisories that describe them appear only with the release. It follows the out-of-band 16.3.6 by eight days, so many projects will upgrade twice in the same month.

Next.jsverified

NEXT.JS16.3.6patches remote code execution in next/og
Toolsstrong signal

Next.js 16.3.6 closes a critical remote code execution hole in next/og

The out-of-band release is available as 16.3.6 on Active LTS and 15.5.26 on Maintenance LTS. Versions from 16.2.0 up to but not including 16.3.6 are affected through the Node.js ImageResponse implementation in next/og, where improper escaping in Satori's SVG output can lead to remote code execution. Applications on the Edge implementation are not affected, and Next.js 15.x does not carry the remote code execution issue at all. The fix works by upgrading the upstream dependencies, Satori among them.

Next.jsverified

Toolsstrong signal

Next.js will ship out-of-band patches on September 22 for a critical upstream flaw

Vercel says a critical security issue has been found in a package that Next.js pulls in. Patched releases 16.3.6 and 15.5.26 are due in an out-of-band update on September 22, 2026. The advisory that spells out impact and affected versions appears only alongside those releases. Until it does, nobody running the framework can size up their own exposure.

Next.jsverified

Toolsmedium signal

A new npm token can submit a release but cannot publish one

GitHub added a permission to npm granular access tokens on September 18, 2026: read and write, stage only. A workflow holding one submits a version to a staging area, and the registry refuses a direct publish from it even when the token is set to bypass two-factor authentication. Releasing the staged version takes a maintainer and a second factor. The deadline behind this is already set, because direct publishing through bypass-2FA tokens is due to disappear in January 2027.

GitHub Changelogverified

Industrystrong signal

An image upload reached OpenAI's internal code, and Claude Opus 5 wrote the exploit

Three researchers at Hacktron chained a memory bug in libheif with a flaw in OpenAI's single sign-on and ended up inside the company's internal code repository. The way in was a HEIC file uploaded to the public community forum. Opus 4.8 could not build a reliable exploit across several sessions; Opus 5, released the same evening, managed it in three hours. OpenAI paid a $6,500 bounty, and the whole chain took less than 72 hours.

Hacktronverified

Toolsstrong signal

The Rust project says maintainers are being lured into video calls that plant malware

The crates.io team and the security response working group published a warning on September 17, 2026: an ongoing campaign is targeting project members and owners of popular crates, with the aim of taking over their devices and accounts and publishing malware through them. The lure is a job, a project or a contract, arranged as a video call. One crate, arrayref, was briefly compromised this way in August. The project says it does not yet know whether the incidents belong to one campaign.

Rust Blogverified

Agentsmedium signal

OpenClaw 2026.8.2 adds a Linux desktop app and widens what sessions see by default

OpenClaw 2026.8.2 was published on September 1, 2026. Two entries in a long set of release notes matter more than the rest: a desktop application for Linux, and a change to what a session may reach by default. Sessions that do not run in a sandbox can now work with other sessions of the same agent unless an operator narrows that. The release also raises the managed Sharp dependency to 0.35.4 with libheif 1.23.2, fixing vulnerabilities in image decoding.

OpenClawverified

Agentsstrong signal

A rumor of a bug is now enough for an agent to write the exploit

Anil Madhavapeddy fixed a path traversal issue in an OCaml library and opened the patch in public, the way maintainers have done for years. About 10 minutes later his own web server was logging probes for that exact pattern. His own agent had already built a working exploit from nothing but a rough description of where to look. The embargo model assumes that keeping the details quiet buys time, and that assumption has stopped holding.

Anil Madhavapeddyverified

Toolsmedium signal

Both SDKs left httpx within eight days, and the plugins had to follow

llm-anthropic 0.27 landed on August 24 and now requires anthropic 1.x, which moved from httpx to httpx2. OpenAI made the same move in its 3.0.0 on August 12, eight days earlier. If you keep both plugins in one environment, they no longer upgrade independently.

Simon Willisonverified

Toolsmedium signal

llm 0.33 takes the pin out and moves to httpx2

Version 0.32.1 held fresh installs together by pinning the OpenAI Python package below 3.0.0. That was a holding action, and 0.33 does the actual repair: it upgrades to the OpenAI library 3.x and switches its HTTP client from httpx to httpx2. The release also carries changes you will notice in daily use, including a --key option on the embedding commands and server-side tool results that finally show up in llm logs.

Simon Willisonverified

Toolsweak signal

A fresh install of llm broke because the OpenAI library stopped using httpx

Version 0.32.1 pins the OpenAI Python package below 3.0.0 so that new installations work again. Nothing in llm changed to cause the break: it imported httpx while relying on the OpenAI package to bring it along, and when that package dropped httpx the dependency simply stopped arriving. It is a small release with a lesson that outlives it.

Simon Willisonverified

Webmedium signal

How Baseline helps you ship less JavaScript

Jad Joubran gives a practical method for auditing package.json: which libraries can be dropped today because the browser does the same job natively. The piece explains Baseline's three states — limited availability, newly available, and widely available — and shows how to use them as a measure instead of a feeling. The gap between the claim that something needs a library and the fact that the browser already does it closes faster than most projects track.

Smashing Magazineverified