How severe is GHSA-594f-3595-c47v?

GHSA-594f-3595-c47v has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-594f-3595-c47v?

GHSA-594f-3595-c47v affects the following packages: github.com/argoproj-labs/terraform-provider-argocd (Go). Ecosystems affected: Go.

How do I fix GHSA-594f-3595-c47v?

Update github.com/argoproj-labs/terraform-provider-argocd to 1.2.3-0.20260316182343-b3364f3f32e7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-594f-3595-c47v is resolved across your whole dependency graph.

How do I detect GHSA-594f-3595-c47v in my Go dependencies?

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

How do I mitigate GHSA-594f-3595-c47v if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-594f-3595-c47v?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-594f-3595-c47v can be triaged on real exposure rather than presence alone.

Is GHSA-594f-3595-c47v actively exploited in the wild?

No public exploit code has been indexed for GHSA-594f-3595-c47v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-594f-3595-c47v published, and has it been updated?

GHSA-594f-3595-c47v was published on March 18, 2026 and was last updated on March 23, 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

MEDIUM severity

GHSA-594f-3595-c47v — terraform-provider-argocd

MEDIUMFix: argoproj-labs/terraform-provider-argocd@b3364f3

GHSA-594f-3595-c47v is a medium-severity (CVSS 4.8) vulnerability in github.com/argoproj-labs/terraform-provider-argocd. A fix is available for github.com/argoproj-labs/terraform-provider-argocd — see the affected versions and patch details below.

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

Also known asGO-2026-4737

Published

Mar 18, 2026

Updated

Mar 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 23, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/argoproj-labs/terraform-provider-argocd

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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/argoproj-labs/terraform-provider-argocd`	all versions	1.2.3-0.20260316182343-b3364f3f32e7`go get github.com/argoproj-labs/terraform-provider-argocd@v1.2.3-0.20260316182343-b3364f3f32e7`

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/argoproj-labs/terraform-provider-argocd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/argoproj-labs/terraform-provider-argocd to 1.2.3-0.20260316182343-b3364f3f32e7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-594f-3595-c47v 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-594f-3595-c47v can be triaged on real exposure rather than presence alone.

Tailored to GHSA-594f-3595-c47v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-594f-3595-c47v in your dependencies?

O3 Security finds GHSA-594f-3595-c47v across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works