CLEANSTART-2026-ME97845: in-memory keyring returned by NewKeyring() silently accepted keys with the ConfirmBeforeUse constraint but never enforced it
CVE-2026-39833 affects multiple packages. The in-memory keyring returned by NewKeyring() silently accepted keys with the ConfirmBeforeUse constraint but never enforced it. See references for individual vulnerability details.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
cleanstart/argo-cdto a version that resolves this vulnerability.Fixed in 3.3.19-r3 - Upgrade
Upgrade
cleanstart/memcached-exporterto a version that resolves this vulnerability.Fixed in 0.18.0-r2
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments using the in-memory keyring created by NewKeyring() are exposed if they rely on the ConfirmBeforeUse constraint to prevent a key from being used without confirmation. The affected software list includes cleanstart/argo-cd and cleanstart/memcached-exporter, but no affected version ranges are provided.
What does an attacker need to exploit this issue?
The supplied severity vector indicates network access, low attack complexity, no privileges, and no user interaction are required. The available data does not describe the specific attack workflow or any additional application-level prerequisites.
How can we determine whether we are affected?
Review whether the deployment uses NewKeyring() and adds or depends on keys carrying the ConfirmBeforeUse constraint. In affected use cases, that constraint may be accepted without being enforced, allowing key use without the expected confirmation.