OpenTofu potential leaking of secret variable values when using static evaluation in v1.8GHSA-wpr2-j6gr-pjw9
LOWGHSA-wpr2-j6gr-pjw9 is a low-severity (CVSS 3.7) CWE-497 vulnerability in github.com/opentofu/opentofu. A fix is available for github.com/opentofu/opentofu — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-wpr2-j6gr-pjw9.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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
Users who have opted into static evaluation of module sources, versions, and backend configurations may be at risk of exposing sensitive variables and locals. This is a workflow that should not be possible and explicitly show errors.
Workarounds
Check that you are not using sensitive variables in module sources and versions, as well as backend configurations. The patch will add explicit errors and prevent this from being possible.
Examples
variable "backend_path" {
type = string
sensitive = true
}
terraform {
backend "local" {
path = var.backend_path
}
}
variable "mod_info" {
type = string
sensitive = true
}
module "foo" {
source = var.mod_info
//version = var.mod_info
}
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/opentofu/opentofu | ≥ 1.8.0&&< 1.8.3 | 1.8.3go get github.com/opentofu/opentofu@v1.8.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/opentofu/opentofu to 1.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wpr2-j6gr-pjw9 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.
Frequently Asked Questions
Is GHSA-wpr2-j6gr-pjw9 in your dependencies?
Find it across Go, including transitive dependencies.