GHSA-q7j3-v8qv-22vq: OpenTofu: Possible arbitrary file read during certain git operations via a maliciously crafted URL
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/opentofu/opentofu (Go) 1.12.3, 1.11.10.
Low priority for now. Upgrade to github.com/opentofu/opentofu (Go) 1.12.3, 1.11.10 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
### 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)
- Published
- Jun 19, 2026
- Updated
- Jun 25, 2026
- EPSS
- —
- CWE
- CWE-1395
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Go | github.com/opentofu/opentofu | pkg:golang/github.com/opentofu/opentofu |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/opentofu/opentofu | from 1.12.0-beta1 · before 1.12.3 | 1.12.3 |
| Go | github.com/opentofu/opentofu | before 1.11.10 | 1.11.10 |
Same product
Go: all recordsOther highest-scoring records for the same primary product.
- GHSA-mjcp-gpgx-ggcgOpenTofu incorrectly validates excluded subdomain constraint in conjunction with TLS certificates containing wildcard SANs23Monitor
- GHSA-pxh5-6rrc-8rjvOpenTofu: Excessive resource usage in "tofu init" when installing dependencies from attacker-controlled server12Monitor
- GHSA-hw5x-4r37-72w7OpenTofu has unbounded memory usage, high CPU usage, or deadlock in "tofu init" with maliciously-crafted dependency responses12Monitor
Published before and after this one in the same product
- ← EarlierGO-2025-4101Nov 17, 2025 · OpenTofu affected denials of service in "tofu init" with maliciously-crafted module package responses in github.com/opentofu/opentofu0Monitor
- ← EarlierGO-2025-4224Dec 15, 2025 · OpenTofu incorrectly validates excluded subdomain constraint in conjunction with TLS certificates containing wildcard SANs in…0Monitor
- Later →GO-2026-5441Jun 25, 2026 · OpenTofu has unbounded memory usage, high CPU usage, or deadlock in "tofu init" with maliciously-crafted dependency responses in…0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/opentofu/opentofu | 1.11.10 | Package registry (OSV) |
| Go:github.com/opentofu/opentofu | 1.12.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- GHSA-mjcp-gpgx-ggcg192 days apartOpenTofu incorrectly validates excluded subdomain constraint in conjunction with TLS certificates containing wildcard SANs23Monitor
- GHSA-hw5x-4r37-72w766 days apartOpenTofu has unbounded memory usage, high CPU usage, or deadlock in "tofu init" with maliciously-crafted dependency responses12Monitor
- GHSA-w2jf-268q-mrvh225 days apartOpenTofu affected denials of service in "tofu init" with maliciously-crafted module package responses12Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-1395 · Dependency on Vulnerable Third-Party ComponentCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- github.com/opentofu/opentofu/pull/4288
- github.com/opentofu/opentofu/pull/4292
- github.com/opentofu/opentofu/pull/4293
- github.com/advisories/GHSA-92mm-2pjq-r785
- github.com/hashicorp/go-getter/releases/tag/v1.8.6
- github.com/opentofu/opentofu
- github.com/opentofu/opentofu/releases/tag/v1.11.10
- github.com/opentofu/opentofu/releases/tag/v1.12.3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.