CLEANSTART-2026-QS77179: Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive CPU exhaustion and memory allocations

Q: Who is exposed to this vulnerability?

Deployments of cleanstart/argo-workflows are exposed where untrusted or attacker-controlled input can reach the ParseAddress, ParseAddressList, or ParseDate functions.

Q: What does an attacker need to exploit it?

An attacker can exploit the issue remotely without privileges or user interaction by supplying well-crafted input that reaches one of the affected parsing functions.

Q: What is the likely impact of exploitation?

Successful exploitation can cause excessive CPU consumption and memory allocation, resulting in a denial-of-service condition. The provided severity vector indicates no confidentiality or integrity impact.

Published Nov 11, 2026

Updated

Security vulnerability affects the argo-workflows package. Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive CPU exhaustion and memory allocations.

Affected Software

1 affected componentFixes available

cleanstart/argo-workflows<4.1.6-r1

4.1.6-r1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade cleanstart/argo-workflows to a version that resolves this vulnerability.
Fixed in 4.1.6-r1

Event History

Nov 11, 2026

Advisory Published

via OSV·12:38 AM

Data Sourced

via OSV·12:38 AM

DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

CVE-2026-39820

Frequently Asked Questions

Who is exposed to this vulnerability?

Deployments of cleanstart/argo-workflows are exposed where untrusted or attacker-controlled input can reach the ParseAddress, ParseAddressList, or ParseDate functions.

What does an attacker need to exploit it?

An attacker can exploit the issue remotely without privileges or user interaction by supplying well-crafted input that reaches one of the affected parsing functions.

What is the likely impact of exploitation?

Successful exploitation can cause excessive CPU consumption and memory allocation, resulting in a denial-of-service condition. The provided severity vector indicates no confidentiality or integrity impact.

CLEANSTART-2026-QS77179: Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive CPU exhaustion and memory allocations

Affected Software

Remediation

Event History

Child vulnerabilities

Frequently Asked Questions

Who is exposed to this vulnerability?

What does an attacker need to exploit it?

What is the likely impact of exploitation?

Company

Resources

Contact

Frequently Asked Questions

Who is exposed to this vulnerability?

What does an attacker need to exploit it?

What is the likely impact of exploitation?