GHSA-q7j3-v8qv-22vq
HIGHOpenTofu: Possible arbitrary file read during certain git operations via a maliciously crafted URL
Blast Radius
github.com/opentofu/opentofu🐹github.com/opentofu/opentofuReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Possible data exposure.
Summary
While downloading packages from a maliciously crafted URL, some git operations against that URL could allow arbitrary file read. This might allow disclosure of confidential information.
Details
OpenTofu relies on go-getter for downloading packages like providers and modules. While doing so from a maliciously crafted URL, the operator could be affected by confidential information disclosure.
The go-getter maintainers have recently published CVE-2026-4660 for this library which indirectly affects OpenTofu's behavior.
Typical use of OpenTofu already requires caution in selection of URLs that are used to download modules and providers.
Patches
OpenTofu v1.11.10 and v1.12.3 address these vulnerabilities by upgrading to the hashicorp/[email protected] that fixes this vulnerability.
The OpenTofu v1.10 series is also impacted by these vulnerabilities. However, that series is built with an older version of the library and upgrading it risks breaking the whole v1.10 series. For those using OpenTofu v1.10 releases, we recommend planning an upgrade to OpenTofu v1.11.10 in the near future.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/opentofu/opentofu | all versions | 1.11.10 |
| 🐹Go | github.com/opentofu/opentofu | ≥ 1.12.0-beta1&&< 1.12.3 | 1.12.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/opentofu/opentofu. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/opentofu/opentofu to 1.11.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q7j3-v8qv-22vq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-q7j3-v8qv-22vq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-q7j3-v8qv-22vq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-q7j3-v8qv-22vq in your dependencies?
O3 detects GHSA-q7j3-v8qv-22vq across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.