Node2Shell Exploited, GitHub Actions Lockfiles, TypeScript 7.1 Beta: Developer News for Early November 2026

The first days of November 2026 bring a mix of urgent security work and useful new tools. A Node.js bug that can turn compressed data into remote code execution is now being targeted in the wild, GitHub made lockfiles for Actions workflows generally available, TypeScript 7.1 is heading toward its release candidate, and AI companies shipped safety settings, new benchmarks and even an IPO filing.

Here is a plain-English summary of each story, what it means for you as a developer or student, and links to the official sources so you can check the details yourself.

1. Node2Shell: Update Node.js Now

On October 21, the Node.js project released security updates for the 26.x, 24.x and 22.x lines. The most serious fix is CVE-2026-111497, an out-of-bounds write in the Brotli decoder bundled with Node.js. According to the advisory, an attacker who can supply Brotli data that an application decompresses with node:zlib can corrupt process memory, which can lead to a crash, disclosure of memory, or remote code execution. Researchers nicknamed it "Node2Shell."

Since then, the story has moved quickly:

• Imperva's research team showed code execution against the official Node.js 24.22.0 Linux arm64 image, using Brotli data in a request or response body. The same inputs were rejected by 24.22.1.
• The threat-intelligence lab ELLIO reproduced it on x86-64 and, on October 26, recorded a crafted exploit attempt against Node.js 24.22.0 on its sensors. As SecurityWeek and The Hacker News report, that attacker's final stage did not produce a shell in ELLIO's 50 tests, but failed attempts can still crash the Node.js process, which makes denial-of-service attacks possible.
• CISA added the flaw to its Known Exploited Vulnerabilities catalog on October 27.

Are you affected? A bare Node.js HTTP server does not decompress request bodies on its own. Exposure depends on what feeds Brotli data to the decoder. Imperva notes that Express 5 and body-parser 2 can decompress incoming Brotli request bodies, and that the built-in fetch() decodes Brotli responses from other servers. So many ordinary web apps and API clients are in scope.

What to do: run node -v and update to 22.23.4, 24.22.1, 26.12.1 or newer. Do not forget Docker images, CI runners and anything else that bundles its own Node binary. If you are still on Node.js 20 or older, those lines are end-of-life and get no patch, so this is the moment to upgrade. PHP developers will recognize the pattern from last week's PHP2Shell emergency.

2. GitHub Actions Workflow Lockfiles Are Generally Available

Most projects reference third-party actions by a tag, like actions/checkout@v4. Tags can be moved, so if an action is compromised and its tag is pointed at malicious code, your next build quietly runs it, with access to your repository secrets. On October 28, GitHub announced that workflow dependency lockfiles are generally available on the Free, Team and Enterprise Cloud plans.

The gh actions-lock extension for the GitHub CLI generates .github/workflows/actions.lock, which records the exact commit of every action your workflows use, including the actions those actions depend on. Your workflow files keep their readable tags, but GitHub Actions runs the locked commits. Dependabot updates the lockfile in the same pull request when it bumps an action, and administrators can enforce adoption with a "Require lockfile" policy. Getting started takes two commands, as described in the GitHub Docs guide:

gh extension install github/gh-actions-lock
gh actions-lock

Review the diff before committing, because the extension may also rewrite your uses: lines to more specific versions. GitHub is clear about the limit: a lockfile protects against unexpected changes, but it does not tell you whether a dependency is safe. It is the same idea as package-lock.json or composer.lock, and it pairs well with regular dependency audits.

3. TypeScript 7.1 Beta: Content Mappers, RC Expected November 10

TypeScript 7.0, the version built on the new Go-based compiler, shipped earlier this year. On October 20 Microsoft announced the TypeScript 7.1 Beta, which you can try with npm install -D typescript@beta.

The headline feature is content mappers, a new plugin point for file types that embed JavaScript or TypeScript, such as Vue single-file components, Svelte, Astro and MDX. A content mapper produces a virtual TypeScript version of the file, with mappings back to the original, so errors and editor features point at the right place in your .vue or .svelte file. Mappers are registered in tsconfig.json. Because they are external programs, running them from the command line requires the explicit tsc --runExternalCode flag, and VS Code only runs them in trusted workspaces. Treat a content mapper like any build plugin: pin its version and know where it comes from. According to Visual Studio Magazine, the beta also lets you declare ambient modules that use import attributes, such as type: "css".

The TypeScript 7.1 iteration plan targets the release candidate for November 10 and the stable release for November 24. These are target dates and can change. If you maintain a library or a framework plugin, now is a good time to test the beta.

4. Claude Code Adds a Hard Limit on Where the Agent Can Write

AI coding agents that edit files on their own are useful, but you usually want them to stay inside the project folder. Claude Code 2.1.314, released October 30, adds a permissions.blockWritesOutsideWorkingDirectories setting. When it is on, the Write, Edit and NotebookEdit tools refuse paths outside the working directories in every permission mode, including modes where the agent normally does not ask for approval.

The setting covers those file-editing tools, so shell commands still need their own limits, such as Claude Code's sandboxed Bash tool. The bigger lesson applies to any AI tool you use: give agents the smallest access they need, and do not rely on the model alone to respect boundaries.

5. Solar v0.3: A Rust Compiler for Solidity

For blockchain developers, Paradigm released Solar v0.3 on November 2. Solar is a Solidity compiler written in Rust, and v0.3 is the first version that generates EVM bytecode. It ships in the Forge toolkit, along with a forge lsp language server. Paradigm reports builds about 100 times faster than the standard solc compiler with via-IR on six real projects, and contracts that use 5% less gas to run. Those are Paradigm's own benchmarks, so expect independent comparisons over the coming weeks.

6. OpenAI's LifeVal Measures Help with Everyday Tasks

Most AI benchmarks test math, coding or exam questions. On November 2, OpenAI introduced LifeVal, an evaluation of everyday tasks such as finding childcare, accessing government services, creating a budget and planning meals. OpenAI says it chose the tasks using the American Time Use Survey, the Multinational Time Use Study, and its own survey of 3,995 respondents about where people want help from a personal assistant. It is OpenAI's own evaluation of its own models, so read the scores as a description of what the company is aiming for, not as an independent ranking. For developers, it is another sign that AI products are moving from chat answers toward agents that take actions in browsers and apps.

7. Anthropic Files for an IPO

On October 26, Anthropic announced that it filed a registration statement on Form S-1 with the U.S. Securities and Exchange Commission for a proposed initial public offering. It plans to list its Class A common stock on the Nasdaq Global Select Market under the symbol ANT. The number of shares and the price range have not been determined yet. For developers who build on Claude, nothing changes today, but the public prospectus will reveal far more about the company's business than was available before.

What This Means for You

• Patch first. If you run anything on Node.js, update to a fixed release today and rebuild your containers.
• Lock your build pipeline. If your projects use GitHub Actions, try gh actions-lock on one repository this week.
• Test before release day. Library and framework authors should try TypeScript 7.1 Beta before the RC lands.
• Fence in your AI agents. Whatever coding assistant you use, check its settings for limits on file writes, shell commands and network access.

Conclusion

This week's common thread is control: control over which Node.js version actually runs in production, which exact code runs in your CI, and what your AI tools are allowed to touch. None of these fixes take long, and each one closes a door attackers are actively looking for. Bookmark the official links above, and check back for our next developer news roundup.