# ArgoCD ServerSideDiff is vulnerable to Kubernetes Secret Extraction Advisory record · `GHSA-3v3m-wc6v-x4x3` - **Identifiers:** `GHSA-3v3m-wc6v-x4x3` · `BIT-argo-cd-2026-42880` · `CVE-2026-42880` · `CVE-2026-43824` · `GO-2026-5099` - **State:** Confirmed - **Severity:** CVSS 9.6 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-201](https://cwe.mitre.org/data/definitions/201.html) · [CWE-212](https://cwe.mitre.org/data/definitions/212.html) · [CWE-312](https://cwe.mitre.org/data/definitions/312.html) - **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-212](https://agentprime.io/advisories/tag/cwe-212.md) - **Published:** 7 May 2026 - **Updated:** 21 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 7 May 2026, 01:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.6: 9.0 or more. How we decide what’s critical: ## Affected packages - `github.com/argoproj/argo-cd/v3` (Go): affected `>=3.2.0, <3.2.11 || >=3.3.0, <3.3.9`; fixed in `3.2.11`, `3.3.9` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Argo CD (github.com/argoproj/argo-cd/v3) versions 3.2.0 before 3.2.11 and 3.3.0 before 3.3.9 are affected. An authenticated user with read-only Argo CD access, such as the default catch-all role, can call the ServerSideDiff endpoint to obtain plaintext Kubernetes Secret data, including tokens, certificates and credentials. This applies to Applications with the IncludeMutationWebhook=true compare option, and the source says extraction works only when a non-Argo CD field manager owns the Secret's data fields. Upgrade to version 3.2.11 or 3.3.9. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 9.6 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0065, the 51st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:11 UTC: First seen by agentprime - 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3v3m-wc6v-x4x3) ## Sources - [GitHub Advisory Database: GHSA-3v3m-wc6v-x4x3](https://github.com/advisories/GHSA-3v3m-wc6v-x4x3) - [OSV: GHSA-3v3m-wc6v-x4x3](https://osv.dev/vulnerability/GHSA-3v3m-wc6v-x4x3) - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .