OpenTofu: Excessive resource usage in "tofu init" when installing dependencies from attacker-controlled server

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact Unauthenticated denial of service. Summary When installing provider or module packages from attacker-controlled servers, the server may cause tofu initto enter an infinite loop sending garbage data to that server. Those who depend on modules or providers served from untrusted third-party servers may experience denial of service due to tofu init failing to complete successfully. Other processes running on the same computer as OpenTofu may also fail or have their performance degraded due to the depletion of shared system resources. These vulnerabilities do not permit arbitrary code execution or allow disclosure of confidential information. Details OpenTofu relies a third-party implementations of HTTP2 from the standard library of the Go programming language. The Go project has recently published the following advisory for that implementation, which indirectly affects OpenTofu's behavior: - CVE-2026-33814: Infinite loop in HTTP/2 transport when given bad SETTINGSMAXFRAMESIZE in…

Published by the source

20 May 2026, 15:35 UTC

Last modified by the source

20 May 2026, 15:35 UTC

Source last checked

26 Oct 2026, 15:22 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-pxh5-6rrc-8rjv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-pxh5-6rrc-8rjv

Advisory: OpenTofu: Excessive resource usage in "tofu init" when installing dependencies from attacker-controlled server
IDs: GHSA-pxh5-6rrc-8rjv
Record: https://patchnext.com/advisories/ghsa-pxh5-6rrc-8rjv (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/opentofu/opentofu 1.11.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/opentofu/opentofu: affected < 1.11.8; fixed in 1.11.8

## Suggested inspection (read-only)
- Go github.com/opentofu/opentofu: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/opentofu/opentofu.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pxh5-6rrc-8rjv (GitHub-reviewed advisory GHSA-pxh5-6rrc-8rjv lists affected ranges: Go github.com/opentofu/opentofu >=0 <1.11.8)

Commands are suggestions: review each one before running it.