Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 7.5, published 19 June 2026.
- Which products and versions are affected?
- OpenTofu < 1.11.10, >= 1.12.0-beta1, < 1.12.3, 1.10.x.
- Is there a fix for This vulnerability?
- A patch was published on 2026-06-19: OpenTofu v1.11.10 and v1.12.3 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run OpenTofu at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
OpenTofu is affected by a vulnerability in its dependency, hashicorp/go-getter (specifically CVE-2026-4660), which is used to download modules and providers. When OpenTofu performs git operations against a maliciously crafted URL, the go-getter library fails to properly sanitize the input, potentially allowing an attacker to read arbitrary files from the local filesystem of the operator. The vulnerability is reachable over the network if an attacker can influence the source URL of a module or provider. The issue is resolved by upgrading go-getter to version 1.8.6, which is included in OpenTofu versions 1.11.10 and 1.12.3.
Affected products
- OpenTofu OpenTofu < 1.11.10, >= 1.12.0-beta1, < 1.12.3, 1.10.x
Timeline
- 2026-06-18: disclosed: Initial report and pull requests submitted
- 2026-06-19: advisory: GitHub Advisory GHSA-q7j3-v8qv-22vq published
- 2026-06-19: patched: OpenTofu v1.11.10 and v1.12.3 released