Terramantle
Get Started Free
Security

Node2Shell and your Terraform providers

One Brotli decoder flaw forced rebuilds of Node.js, .NET, Python packages and Bun, each on its own schedule. Terraform providers are statically linked Go binaries with the same shape of exposure, and only the upstream maintainer can rebuild them. This page covers what that means for a Terraform estate and what a registry can do about it.

On 21 October 2026 the Node.js project disclosed CVE-2026-111497, an out-of-bounds write in Google's Brotli decoder that can lead to remote code execution. Google scored it 9.2 on CVSS 4.0. The fix landed in Node.js 22.23.4, 24.22.1 and 26.12.1, in Brotli 1.0.10, 1.1.1 and 1.2.1, and then in Microsoft .NET, Visual Studio and PowerShell, in Python packages, and in Bun 1.4.4. CISA added it to the Known Exploited Vulnerabilities catalogue with a federal remediation deadline of 10 November 2026, and sensor networks reported exploit traffic in the wild. The names varied, Node2Shell, HTTP2Shell, Broccoli2Shell, but the shape was constant: one C library, embedded in dozens of runtimes, each of which had to cut and ship its own release.

The same thing happens whenever a library is compiled into the program that uses it rather than loaded beside it. Terraform providers are the purest example of that in an infrastructure team's estate.

What is inside a provider binary

The exposure is a vulnerability in code you didn't write, shipped inside a binary you didn't build, that runs with your cloud credentials.

When hashicorp/aws or any other provider is released, the Go toolchain compiles every imported module into one executable: golang.org/x/net, google.golang.org/grpc, the cloud SDK, the Terraform plugin framework, and everything those import. There is no shared library to patch underneath it. A fix in x/net reaches your pipeline only when the provider's maintainer bumps the dependency, rebuilds and publishes a new version, and when you then move your constraint to it.

This has already happened at ecosystem scale. In October 2023 the HTTP/2 Rapid Reset vulnerability, CVE-2023-39325, was fixed in golang.org/x/net. Every provider that vendored the affected version carried it, and each one was remediated on its own maintainer's release cadence. A team pinning a provider that had gone quiet carried it indefinitely.

Detection: re-reading the SBOM when the database changes

On the morning an advisory lands, the first question is which of your provider versions are affected.

Every provider version Terramantle scans produces an SPDX software bill of materials with trivy, stored against the version. A version's source does not change between scans; only the vulnerability database does. So the CVE refresh re-evaluates the stored SBOMs against the current database daily, with no clone and no rebuild, and a newly published CVE appears as a finding on each affected version. The refresh also checks the upstream tag with git ls-remote, so a tag that has been moved is noticed rather than trusted.

This is a per-version re-evaluation, and the result is a set of findings on each version. There is no endpoint that takes a package name and returns every version containing it. On a Node2Shell morning you open the provider, see which versions now carry the finding, and see which workspaces have those versions in their lock files. You don't have a one-line fleet query.

Decision: from a KEV listing to a deny

A listed, exploited CVE can sit in a backlog because its CVSS looked ordinary, or because the team that owns the provider pin isn't the team that reads advisories.

The provider policy input carries scan.vulnerabilities.kev_count, and each finding carries meta.kev, "True when this CVE is on the CISA Known Exploited Vulnerabilities catalogue, i.e. exploited in the wild, not merely scored." The baseline template "Block actively exploited CVEs" denies on that flag whatever the score. If the org has set on_missing_signal to hard_fail, a version scanned while the catalogue was unavailable is also denied, because a null count is "a missing signal, not a zero."

An enforcing deny stops the version being served to the org. A blocked version answers 404 rather than 403, because "A blocked provider must not advertise that it exists for this org." The refusal is written to the decision ledger. The KEV policy page has the Rego in full.

Remediation: rebuilding the version you already pin

Sometimes the fix exists in the library and in no released provider version you can move to.

The auto-patch endpoint "applies the scanner's dependency fixes to the upstream release tag in a private fork, then builds and publishes the result as a new revision. Same-major bumps only." The patch is "always applied fresh from the upstream tag, never on top of a previous patched tree." The result is tagged <base>-0.0.<rev>, smoke-built, run through govulncheck and then through the same gates and signing as any other self-built provider. The comparison endpoint shows what the patch "fixed", what "remains" and anything it "introduced", with the fork repository, both commit SHAs and a diff URL.

Because Terraform and OpenTofu drop prereleases from range constraints, a request for the base version is answered with the patched revision when substitution is enabled. It is enabled as of the review date. The constraint in your required_providers does not change; the bytes behind it do, and the lock file records the new hashes.

StageStatus on the review date
SBOM generation per provider versionLive
Daily CVE refresh against stored SBOMsLive since 2026-10-21
KEV flag and count in policy inputLive
Patched build on explicit triggerLive
Fleet-wide auto-patch schedulerPaused
Substitution of patched revision for range requestsLive

What this does not do

It does not cover Node2Shell itself, which is a runtime flaw in your applications and build images rather than in your providers. The inventory question it raises is the subject of the patch-day inventory page. It does not patch a provider's own code, only its Go dependencies, and only within the same major. It does not offer a fleet-wide "which versions contain this package" query; the findings are per version. The scheduler that would patch across the fleet without a human trigger is paused. And a patched revision is signed with a software key whose limits are set out on the provenance page. What the registry changes is the dependency on the upstream release calendar, for one class of flaw: a vulnerability in a vendored Go library.

Node2Shell and providers FAQ

Does Node2Shell affect Terraform providers?

Not directly. Node2Shell is a flaw in the Brotli decoder as used by Node.js and other runtimes. Terraform providers are Go binaries. The relevance is the pattern: one library, vendored into many products, each of which had to ship its own rebuild. Go providers have the same pattern, and the on-record precedent is the HTTP/2 Rapid Reset vulnerability, CVE-2023-39325, in golang.org/x/net.

How would I find out which provider versions carry a newly published CVE?

Each scanned provider version has a stored SPDX SBOM. The daily CVE refresh re-evaluates those SBOMs against the current vulnerability database, so the affected versions show the new finding without a re-scan. There is no single query for "which versions contain package X"; the answer is the per-version findings, which the portal and policies read.

What does a KEV listing change?

A finding whose CVE is on the CISA KEV catalogue carries kev: true and the version carries a non-zero kev_count. The baseline template "Block actively exploited CVEs" denies on that, whatever the CVSS score. If the template is enforcing, the version stops being served to the org.

Can Terramantle ship a fix before upstream does?

For a vulnerability in a Go dependency with a same-major fix available, yes: a patched revision is built as one commit off the upstream tag with the dependency bumped. For a flaw in the provider's own code, or one that only a major bump fixes, no.

Is the patching automatic?

Explicit triggers are live. The fleet-wide scheduler is paused as of the review date for capacity reasons recorded in the worker configuration. Substitution of a patched revision for a range request is enabled.

Last reviewed

Terramantle is a private Terraform and OpenTofu registry. See pricing or read the FAQ.