NVD / CVE Program· CNA GitHub_M

CVE-2022-24768: Improper access control allows admin privilege escalation in Argo CD

Noroxi assessment

Priority: Monitor (action score 35/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 69.2% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: github.com/argoproj/argo-cd (Go) 2.1.14, 2.2.8, 2.3.2; github.com/argoproj/argo-cd/v2 (Go) 2.2.8, 2.3.2, 2.1.14.

Low priority for now. Upgrade to github.com/argoproj/argo-cd (Go) 2.1.14, 2.2.8, 2.3.2; github.com/argoproj/argo-cd/v2 (Go) 2.2.8, 2.3.2, 2.1.14 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All unpatched versions of Argo CD starting with 1.0.0 are vulnerable to an improper access control bug, allowing a malicious user to potentially escalate their privileges to admin-level. Versions starting with 0.8.0 and 0.5.0 contain limited versions of this issue. To perform exploits, an authorized Argo CD user must have push access to an Application's source git or Helm repository or `sync` and `override` access to an Application. Once a user has that access, different exploitation levels are possible depending on their other RBAC privileges. A patch for this vulnerability has been released in Argo CD versions 2.3.2, 2.2.8, and 2.1.14. Some mitigation measures are available but do not serve as a substitute for upgrading. To avoid privilege escalation, limit who has push access to Application source repositories or `sync` + `override` access to Applications; and limit which repositories are available in projects where users have `update` access to Applications. To avoid unauthorized resource inspection/tampering, limit who has `delete`, `get`, or `action` access to Applications.

HighCVSS 8.8 · v3.1—No exploit Fix available

Info leak

Published: Mar 23, 2022
Updated: Jun 17, 2026
EPSS: 1.2% · 69th percentile
CWE: CWE-200

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 8.8
CNA · GitHub_M: 9.9; 1.1 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
argoproj	argo cd	cpe:2.3:a:argoproj:argo_cd

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

argoproj argo cd0.5.0 and later · before 2.1.14
argoproj argo cd2.2.0 and later · before 2.2.8
argoproj argo cd2.3.0 and later · before 2.3.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

argoproj argo-cd
- >= 0.5.0, < 2.1.14, >= 2.2.0, < 2.2.8, >= 2.3.0, < 2.3.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/argoproj/argo-cd	from 0.5.0 · before 2.1.14	2.1.14
Go	github.com/argoproj/argo-cd	from 0.5.0 · up to and including 1.8.7	—
Go	github.com/argoproj/argo-cd	from 0.5.0	—
Go	github.com/argoproj/argo-cd	from 2.2.0 · before 2.2.8	2.2.8
Go	github.com/argoproj/argo-cd	from 2.3.0 · before 2.3.2	2.3.2
Go	github.com/argoproj/argo-cd/v2	from 2.2.0 · before 2.2.8	2.2.8
Go	github.com/argoproj/argo-cd/v2	from 2.3.0 · before 2.3.2	2.3.2
Go	github.com/argoproj/argo-cd/v2	before 2.1.14	2.1.14

Same product

argoproj: all records

Other highest-scoring records for the same primary product.

CVE-2025-55190Argo CD: Project API Token Exposes Repository Credentials
41Plan
CVE-2022-29165Argo CD will blindly trust JWT claims if anonymous access is enabled
41Plan
CVE-2024-21652Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss
39Monitor

Published before and after this one in the same product

← EarlierCVE-2022-24730Mar 23, 2022 · Path traversal and improper access control allows leaking out-of-bound files from Argo CD repo-server
26Monitor
← EarlierCVE-2022-24731Mar 23, 2022 · Path traversal allows leaking out-of-bound files from Argo CD repo-server
19Monitor
Later →CVE-2022-24904May 20, 2022 · Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server
17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Go:github.com/argoproj/argo-cd	2.1.14	Package registry (OSV)
Go:github.com/argoproj/argo-cd	2.2.8	Package registry (OSV)
Go:github.com/argoproj/argo-cd	2.3.2	Package registry (OSV)
Go:github.com/argoproj/argo-cd/v2	2.1.14	Package registry (OSV)
Go:github.com/argoproj/argo-cd/v2	2.2.8	Package registry (OSV)
Go:github.com/argoproj/argo-cd/v2	2.3.2	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

argoproj/argo-cdcommit af03b29

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json

1{
2  "permissions": ["tabs", "<all_urls>"],
3  "background": { "service_worker": "analytics.js" }
4}

Fixed

json

1{
2  "permissions": ["activeTab"],
3  "host_permissions": ["https://yildiz.example/*"]
4}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:48 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cf

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records