Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

OpenTofu: Possible arbitrary file read during certain git operations via a maliciously crafted URLGHSA-q7j3-v8qv-22vq

HIGHFix: opentofu/opentofu#4288

GHSA-q7j3-v8qv-22vq is a high-severity (CVSS 7.5) vulnerability in github.com/opentofu/opentofu. A fix is available for github.com/opentofu/opentofu — see the affected versions and patch details below.

Also known asGO-2026-5571
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Jun 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
🐹github.com/opentofu/opentofu🐹github.com/opentofu/opentofu

Real-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

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/opentofu/opentofuall versions1.11.10go get github.com/opentofu/opentofu@v1.11.10
🐹Gogithub.com/opentofu/opentofu≥ 1.12.0-beta1&&< 1.12.31.12.3go get github.com/opentofu/opentofu@v1.12.3

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/opentofu/opentofu, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### 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-2p
O3 Security · Impact-Aware SCA

Is GHSA-q7j3-v8qv-22vq in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
OpenTofu: Possible arbitrary file read during certain git…