Skip to content
Fencer Intel
medium 6.3

CVE-2026-45737 json

Argo CD: Kubernetes Secret Extraction via ArgoCD ServerSideDiff via sensitive annotations

published 5mo ago modified 16d ago also BIT-argo-cd-2026-45737 , EUVD-2026-44792 , GHSA-rg3g-4rw9-gqrp , GO-2026-5618

cvss
6.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 3.2.0 until 3.2.12, 3.3.10, and 3.4.2, Argo CD ServerSideDiff can expose Kubernetes Secret values embedded in the kubectl.kubernetes.io/last-applied-configuration annotation because HideSecretData(target, live, ...) does not fully sanitize ResourceDiff.TargetState and LiveState predicted live Secret objects, allowing sensitive data, stringData, and annotations to appear in UI or CLI diffs. This issue is fixed in versions 3.2.12, 3.3.10, and 3.4.2.

Patch / fix

  • go github.com/argoproj/argo-cd/v3 3.2.12, 3.3.10, 3.4.2
  • bitnami argo-cd 3.2.12, 3.3.10, 3.4.2
  • linuxfoundation argo-cd 3.2.12, 3.3.10, 3.4.2
  • linuxfoundation argo_continuous_delivery 3.2.12, 3.3.10, 3.4.2
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2026-45737 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

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
3mo ago

Exploit prediction

0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/argoproj/argo-cd/security/advisories/GHSA-rg3g-4rw9-gqrp referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 6.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd/v3
>=3.2.0, <3.2.12
>=3.3.0-rc1, <3.3.10
>=3.4.0-rc1, <3.4.2
3.2.12
3.3.10
3.4.2
bitnami argo-cd
>=3.2.0, <3.2.12
>=3.3.9, <3.3.10
>=3.4.1, <3.4.2
3.2.12
3.3.10
3.4.2
go github.com/argoproj/argo-cd
all versions
 no fix listed
go github.com/argoproj/argo-cd/v2
all versions
 no fix listed

Affected products

  • argoproj argo-cd

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-212 Improper Removal of Sensitive Information Before Storage or Transfer

References

Sources

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.