# CVE-2026-43824: Information disclosure in Argo CD

> Attackers can read cleartext Kubernetes Secret data via ServerSideDiff in Argo CD, exposing sensitive credentials.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 May 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-c7mp-5hg2-gfh8

## What is CVE-2026-43824?

CVE-2026-43824 is a high-severity vulnerability in argoproj Argo CD, published on 2 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Argo CD 3.2.0 before 3.2.11 and 3.3.0 before 3.3.9, ServerSideDiff allows reading cleartext Kubernetes Secret data.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information), CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

## Which versions are affected by CVE-2026-43824?


## How do I fix CVE-2026-43824?

Upgrade to a fixed version.

## Is CVE-2026-43824 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43824 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43824 and fix it if it is affected.

What it is: CVE-2026-43824 is a high-severity vulnerability in argoproj Argo CD, published on 2 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43824 exists.

Affected product: argoproj Argo CD. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43824/ (Markdown: https://insights.sbomify.com/CVE-2026-43824/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43824
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43824
- OSV: https://osv.dev/vulnerability/CVE-2026-43824

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43824/
Summaries are generated and may contain mistakes; the official description above is the record.