Terraform Provider for ArgoCD has possible exposure to GO-2026-4337 / CVE-2025-68121

published 2026-03-18 7mo ago modified 2026-03-23 7mo ago also GO-2026-4737

cvss: 4.8; 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 The terraform-provider-argocd might have been vulnerable to GO-2026-4337 / CVE-2025-68121 ("Unexpected session resumption in crypto/tls").

### Details

See https://pkg.go.dev/vuln/GO-2026-4337 for the upstream vulnerability.

Provider versions starting with `v7.15.1` are using `go 1.25.8` for building and are thus no longer affected.

Patch / fix

fixed in 1 links 1

go github.com/argoproj-labs/terraform-provider-argocd 1.2.3-0.20260316182343-b3364f3f32e7

github.com/argoproj-labs/terraform-provider-argocd@b3364f3 commit

Is GHSA-594f-3595-c47v 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 Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	4.8	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
go	github.com/argoproj-labs/terraform-provider-argocd	<1.2.3-0.20260316182343-b3364f3f32e7	1.2.3-0.20260316182343-b3364f3f32e7

Classification

Weakness

CWE-1395 Dependency on Vulnerable Third-Party Component
CWE-295 Improper Certificate Validation

References

Sources

GitHub Advisory GHSA-594f-3595-c47v
OSV GO-2026-4737

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.