# CVE-2026-6388: Argocd-image-updater: argocd image updater: cross-namespace privilege escalation via insufficient namespace validation

> Attackers with resource creation permissions can bypass namespace boundaries to trigger unauthorized image updates on other tenants' applications.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-mx9c-q7m4-fm97

## What is CVE-2026-6388?

CVE-2026-6388 is a critical vulnerability in Red Hat OpenShift GitOps, published on 15 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in ArgoCD Image Updater. This vulnerability allows an attacker, with permissions to create or modify an ImageUpdater resource in a multi-tenant environment, to bypass namespace boundaries. By exploiting insufficient validation, the attacker can trigger unauthorized image updates on applications managed by other tenants. This leads to cross-namespace privilege escalation, impacting application integrity through unauthorized application updates.

Weakness: CWE-1220 (Insufficient Granularity of Access Control)

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


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

No fix has been published for CVE-2026-6388 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6388 being exploited?

There is no known exploitation of CVE-2026-6388 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6388 is a critical vulnerability in Red Hat OpenShift GitOps, published on 15 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6388 in the wild and no public exploit code.

Affected product: Red Hat OpenShift GitOps. 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-6388/ (Markdown: https://insights.sbomify.com/CVE-2026-6388/index.md)
```

## Sources

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

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