GHSA-q7j3-v8qv-22vq json
OpenTofu: Possible arbitrary file read during certain git operations via a maliciously crafted URL
published 4mo ago modified 4mo ago also GO-2026-5571
- cvss
- 7.5
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### 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](https://github.com/hashicorp/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](https://github.com/advisories/GHSA-92mm-2pjq-r785) 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/go-getter@v1.8.6](https://github.com/hashicorp/go-getter/releases/tag/v1.8.6) 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 * [Initial report](https://github.com/opentofu/opentofu/pull/4288) * [CVE-2026-4660](https://github.com/advisories/GHSA-92mm-2pjq-r785) * [OpenTofu v1.12 patch](https://github.com/opentofu/opentofu/pull/4293) * [OpenTofu v1.11 patch](https://github.com/opentofu/opentofu/pull/4292) * [Patched v1.12.3 version](https://github.com/opentofu/opentofu/releases/tag/v1.12.3) * [Patched v1.11.10 version](https://github.com/opentofu/opentofu/releases/tag/v1.11.10)
Patch / fix
- go github.com/opentofu/opentofu 1.11.10, 1.12.3
- github.com/opentofu/opentofu#4288 pull request
- github.com/opentofu/opentofu#4292 pull request
- github.com/opentofu/opentofu#4293 pull request
- github.com/hashicorp/go-getter/releases/tag/v1.8.6 release
- github.com/opentofu/opentofu/releases/tag/v1.11.10 release
- github.com/opentofu/opentofu/releases/tag/v1.12.3 release
Is GHSA-q7j3-v8qv-22vq in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/opentofu/opentofu | <1.11.10 >=1.12.0-beta1, <1.12.3 |
1.11.10 1.12.3 |
Classification
- Weakness
-
- CWE-1395 Dependency on Vulnerable Third-Party Component
References
-
github.com
/opentofu/opentofu/pull/4288
web, patch
-
github.com
/opentofu/opentofu/pull/4292
web, patch
-
github.com
/opentofu/opentofu/pull/4293
web, patch
-
github.com
/opentofu/opentofu/security/advisories/GHSA-q7j3-v8qv-22vq
web, advisory
-
github.com
/advisories/GHSA-92mm-2pjq-r785
advisory, web
-
github.com
/hashicorp/go-getter/releases/tag/v1.8.6
web
-
github.com
/opentofu/opentofu
package
-
github.com
/opentofu/opentofu/releases/tag/v1.11.10
web
-
github.com
/opentofu/opentofu/releases/tag/v1.12.3
web
Sources
- GitHub Advisory GHSA-q7j3-v8qv-22vq
- OSV GO-2026-5571
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.