Cyber Resilience

CVE-2025-59538

Argoproj Argo Cd 2.9.0 – 2.14.20

Public PoC
Published
01 October 2025
Modified
07 October 2025
Patch / advisory
View advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.083 94th percentile
Risk Priority 66 floored blend · peak EPSS

Summary

CVE-2025-59538 is a high-severity Uncaught Exception (CWE-248) vulnerability in Argoproj Argo Cd. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-24 (Fail in Known State) and SI-17 (Fail-safe Procedures) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A10:2025 Mishandling of Exceptional Conditions

EU & UK References

Vulnerability Data

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. For versions 2.9.0-rc1 through 2.14.19, 3.0.0-rc1 through 3.2.0-rc1, 3.1.6 and 3.0.17, when the webhook.azuredevops.username and webhook.azuredevops.password are not set in the default configuration, the /api/webhook endpoint crashes the entire…

more

argocd-server process when it receives an Azure DevOps Push event whose JSON array resource.refUpdates is empty. The slice index [0] is accessed without a length check, causing an index-out-of-range panic. A single unauthenticated HTTP POST is enough to kill the process. This issue is resolved in versions 2.14.20, 3.2.0-rc2, 3.1.8 and 3.0.19.

CWE(s)
CWE-248CWE-703

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-59531Same product: Argoproj Argo Cd
CVE-2025-59537Same product: Argoproj Argo Cd
CVE-2024-21661Same product: Argoproj Argo Cd
CVE-2023-22736Same product: Argoproj Argo Cd
CVE-2023-22482Same product: Argoproj Argo Cd
CVE-2024-31990Same product: Argoproj Argo Cd
CVE-2023-23947Same product: Argoproj Argo Cd
CVE-2023-50726Same product: Argoproj Argo Cd
CVE-2023-40026Same product: Argoproj Argo Cd
CVE-2025-55191Same product: Argoproj Argo Cd

Affected Assets

argoproj
argo cd
3.2.0 · 2.9.0 — 2.14.20 · 3.0.0 — 3.0.19 · 3.1.0 — 3.1.8

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-24 Fail in Known State good match

Enforces failure to a known state while preserving required properties, limiting impact of unhandled exceptions.

SI-17 Fail-safe Procedures good match

Mandates explicit fail-safe procedures triggered by indicated failures, structurally preventing unhandled exceptional conditions.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles include robust exception management to keep the system in a defined state.

SI-11 Error Handling partial match

Error handling requirements force structured catching and response to exceptions instead of allowing them to propagate uncaught.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices explicitly require structured exception handling to prevent uncaught exceptions from reaching production.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect uncaught exceptions before production deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes exception-handling standards that reduce uncaught exceptions.

A.8.26 Application security requirements partial match
prevents

Application security requirements typically mandate robust error and exception handling.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles call for centralized, comprehensive exception management.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require catching and handling exceptions to prevent crashes or leaks.

A.6.8 Information security event reporting none match
none

Reporting of unhandled errors or exceptional conditions surfaces latent failure paths so they can be corrected before exploitation.

References