CLEANSTART-2026-QB68616: When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as fo...

Published Nov 19, 2026
·
Updated

Security vulnerability affects the argo-cd package. When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as force-command after a second factor succeeded.

Affected Software

1 affected componentFixes available
cleanstart/argo-cd<3.6.1-r3
3.6.1-r3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade cleanstart/argo-cd to a version that resolves this vulnerability.

    Fixed in 3.6.1-r3

Event History

Nov 19, 2026
Advisory Published
via OSV·12:35 AM
Data Sourced
via OSV·12:35 AM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Who is exposed to this issue?

Deployments of the affected argo-cd package that use an SSH server authentication callback returning PartialSuccessError with non-nil Permissions are exposed. The risk is especially relevant where SSH certificate restrictions, such as force-command, are expected to remain in effect after multi-factor authentication.

2

What conditions are required for exploitation?

An attacker needs network access to the SSH service and low-privileged authentication capability. Exploitation depends on the authentication flow reaching a PartialSuccessError with non-nil Permissions before a second factor succeeds.

3

Are default deployments known to be affected?

The available information does not establish whether the affected callback behavior is enabled or reachable in a default configuration. Exposure depends on the SSH authentication callback and multi-factor authentication flow in use.

4

What can be done if patching is not immediately possible?

Review SSH authentication flows that use PartialSuccessError and avoid relying on certificate permissions or restrictions being preserved across a second authentication factor. Restrict network access to the SSH service and limit low-privileged accounts that can begin authentication.

5

How can I determine whether my deployment is affected?

Inspect the SSH server authentication callback for cases where it returns PartialSuccessError together with non-nil Permissions. Confirm whether certificate restrictions, including force-command, are expected to persist after the second factor completes.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203