CLEANSTART-2026-AW58083: source-address critical option in the Permissions returned by an authentication callback was only enforced for the PublicKeyCallback and VerifiedPublicKeyCallback paths, extending the fix for CVE-2...

Published Nov 20, 2026
·
Updated

CVE-2026-56854 affects multiple packages. The source-address critical option in the Permissions returned by an authentication callback was only enforced for the PublicKeyCallback and VerifiedPublicKeyCallback paths, extending the fix for CVE-2026-46595. See references for individual vulnerability details.

Affected Software

4 affected componentsFixes available
cleanstart/tempo<2.9.5-r3
2.9.5-r3
cleanstart/openbao<2.5.5-r2
2.5.5-r2
cleanstart/argo-cd<3.3.19-r3
3.3.19-r3
cleanstart/memcached-exporter<0.18.0-r2
0.18.0-r2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade cleanstart/tempo to a version that resolves this vulnerability.

    Fixed in 2.9.5-r3
  2. Upgrade

    Upgrade cleanstart/openbao to a version that resolves this vulnerability.

    Fixed in 2.5.5-r2
  3. Upgrade

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

    Fixed in 3.3.19-r3
  4. Upgrade

    Upgrade cleanstart/memcached-exporter to a version that resolves this vulnerability.

    Fixed in 0.18.0-r2

Event History

Nov 20, 2026
Advisory Published
via OSV·12:44 AM
Data Sourced
via OSV·12:44 AM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Which deployments are potentially exposed?

Deployments using cleanstart/tempo, cleanstart/openbao, cleanstart/argo-cd, or cleanstart/memcached-exporter are identified as affected by this advisory. The issue concerns authentication callback paths that return Permissions containing the source-address critical option.

2

What authentication conditions are required for exploitation?

The vulnerable condition applies when an authentication callback returns Permissions with the source-address critical option and the connection uses a path other than PublicKeyCallback or VerifiedPublicKeyCallback. The provided data does not identify which specific alternative callback paths are affected.

3

Are source-address restrictions consistently enforced across authentication callback paths?

No. The source-address critical option was enforced only for the PublicKeyCallback and VerifiedPublicKeyCallback paths, meaning other authentication callback paths did not enforce that restriction.

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