How severe is CVE-2023-34236?

CVE-2023-34236 has a CVSS score of 8.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-34236?

CVE-2023-34236 affects the following packages: github.com/weaveworks/tf-controller (Go), github.com/weaveworks/tf-controller (Go). Ecosystems affected: Go.

How do I fix CVE-2023-34236?

Update github.com/weaveworks/tf-controller to 0.14.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-34236 is resolved across your whole dependency graph.

How do I detect CVE-2023-34236 in my Go dependencies?

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

How do I mitigate CVE-2023-34236 if there is no patch (or I can't update yet)?

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.

Is CVE-2023-34236 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2023-34236, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-34236?

CVE-2023-34236 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-34236?

CVE-2023-34236 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-34236 published, and has it been updated?

CVE-2023-34236 was published on July 14, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2023-34236 — tf-controller

HIGHFix: weaveworks/tf-controller@28282bc

CVE-2023-34236 is a high-severity (CVSS 8.5) Information Exposure vulnerability in github.com/weaveworks/tf-controller. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for github.com/weaveworks/tf-controller — see the affected versions and patch details below.

Information Disclosure Vulnerability in Weave GitOps Terraform Controller

Also known asGHSA-6hvv-j432-23cvGO-2023-1925

Published

Jul 14, 2023

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

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 CVE-2023-34236.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

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

2 pkgs affected

🐹github.com/weaveworks/tf-controller🐹github.com/weaveworks/tf-controller

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

A vulnerability has been identified in Weave GitOps Terraform Controller which could allow an authenticated remote attacker to view sensitive information. This vulnerability stems from Weave GitOps Terraform Runners (tf-runner), where sensitive data is inadvertently printed - potentially revealing sensitive user data in their pod logs. In particular, functions tfexec.ShowPlan, tfexec.ShowPlanRaw, and tfexec.Output are implicated when the tfexec object set its Stdout and Stderr to be os.Stdout and os.Stderr.

An unauthorized remote attacker could exploit this vulnerability by accessing these prints of sensitive information, which may contain configurations or tokens that could be used to gain unauthorized control or access to resources managed by the Terraform controller.

A successful exploit could allow the attacker to utilize this sensitive data, potentially leading to unauthorized access or control of the system.

Patches

This vulnerability has been addressed in Weave GitOps Terraform Controller versions v0.14.4 and v0.15.0-rc.5. Users are urged to upgrade to one of these versions to mitigate the vulnerability.

The patches for this vulnerability are found in:

this commit: 9708fda28ccd0466cb0a8fd409854ab4d92f7dca
this commit: 6323b355bd7f5d2ce85d0244fe0883af3881df4e
this commit: 28282bc644054e157c3b9a3d38f1f9551ce09074
and this commit: 98a0688036e9dbcf43fa84960d9a1ef3e09a69cf

Workarounds

As a temporary measure until the patch can be applied, users can add the environment variable DISABLE_TF_LOGS to the tf-runners via the runner pod template of the Terraform Custom Resource. This will prevent the logging of sensitive information and mitigate the risk of this vulnerability.

References

The first issue: https://github.com/weaveworks/tf-controller/issues/637
The second issue: https://github.com/weaveworks/tf-controller/issues/649

For More Information

If you have any further questions or comments about this advisory:

Open an issue in the Weave GitOps Terraform Controller repository Email us at [email protected]

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/weaveworks/tf-controller`	all versions	0.14.4`go get github.com/weaveworks/tf-controller@v0.14.4`
🐹Go	`github.com/weaveworks/tf-controller`	≥ 0.15.0-rc.1&&< 0.15.0-rc.5	0.15.0-rc.5`go get github.com/weaveworks/tf-controller@v0.15.0-rc.5`

Affected Products

1 product · 5 configurations

Application

gitops terraform controllerweave

< 0.14.4

1 version

0.15.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Weave GitOps Terraform Controller (aka Weave TF-controller) is a control…

github.comNVDJul 2023

Report on github.com

github.comNVDJul 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/weaveworks/tf-controller, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/weaveworks/tf-controller to 0.14.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-34236 is resolved across your whole dependency graph.
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 A vulnerability has been identified in Weave GitOps Terraform Controller which could allow an authenticated remote attacker to view sensitive information. This vulnerability stems from Weave GitOps Terraform Runners (`tf-runner`), where sensitive data is inadvertently printed - potentially revealing sensitive user data in their pod logs. In particular, functions `tfexec.ShowPlan`, `tfexec.ShowPlanRaw`, and `tfexec.Output` are implicated when the `tfexec` object set its `Stdout` and `Stderr` to be `os.Stdout` and `os.Stderr`. An unauthorized remote attacker could exploit this vulne