CLEANSTART-2026-NI84143: Spring Framework applications that use Spring's data binding infrastructure to apply user-supplied property paths onto a target object may be vulnerable to a Denial of Service (DoS) attack

Q: Which Rundeck deployments are exposed to this issue?

The affected software is identified as cleanstart/rundeck. Exposure depends on whether the application uses Spring's data binding infrastructure to apply user-supplied property paths to a target object; the provided data does not identify specific affected versions or configurations.

Q: What does an attacker need to exploit the vulnerability?

An attacker needs network access and does not require privileges or user interaction, according to the supplied CVSS vector. Exploitation involves supplying property paths to a vulnerable Spring data-binding flow.

Q: What is the expected impact?

The stated impact is denial of service. The supplied vector indicates no confidentiality or integrity impact, while availability impact is high.

Q: How can I determine whether my deployment is affected?

Review whether the Rundeck deployment includes a Spring data-binding path that accepts user-supplied property paths and applies them to target objects. The provided advisory data does not include affected version ranges, fixed versions, or detection indicators.

Published Nov 11, 2026

Updated

Security vulnerability affects the rundeck package. Spring Framework applications that use Spring's data binding infrastructure to apply user-supplied property paths onto a target object may be vulnerable to a Denial of Service (DoS) attack.

Affected Software

2 affected componentsFixes available

cleanstart/rundeck<6.3.0-r0

6.3.0-r0

cleanstart/rundeck<6.1.0-r4

6.1.0-r4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade cleanstart/rundeck to a version that resolves this vulnerability.
Fixed in 6.3.0-r0
Upgrade
Upgrade cleanstart/rundeck to a version that resolves this vulnerability.
Fixed in 6.1.0-r4

Event History

Nov 11, 2026

Advisory Published

via OSV·12:39 AM

Data Sourced

via OSV·12:39 AM

DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

CVE-2026-59282

Frequently Asked Questions

Which Rundeck deployments are exposed to this issue?

The affected software is identified as cleanstart/rundeck. Exposure depends on whether the application uses Spring's data binding infrastructure to apply user-supplied property paths to a target object; the provided data does not identify specific affected versions or configurations.

What does an attacker need to exploit the vulnerability?

An attacker needs network access and does not require privileges or user interaction, according to the supplied CVSS vector. Exploitation involves supplying property paths to a vulnerable Spring data-binding flow.

What is the expected impact?

The stated impact is denial of service. The supplied vector indicates no confidentiality or integrity impact, while availability impact is high.

How can I determine whether my deployment is affected?

Review whether the Rundeck deployment includes a Spring data-binding path that accepts user-supplied property paths and applies them to target objects. The provided advisory data does not include affected version ranges, fixed versions, or detection indicators.

CLEANSTART-2026-NI84143: Spring Framework applications that use Spring's data binding infrastructure to apply user-supplied property paths onto a target object may be vulnerable to a Denial of Service (DoS) attack

Affected Software

Remediation

Event History

Child vulnerabilities

Frequently Asked Questions

Which Rundeck deployments are exposed to this issue?

What does an attacker need to exploit the vulnerability?

What is the expected impact?

How can I determine whether my deployment is affected?

Company

Resources

Contact

Frequently Asked Questions

Which Rundeck deployments are exposed to this issue?

What does an attacker need to exploit the vulnerability?

What is the expected impact?

How can I determine whether my deployment is affected?