YAOOK Security Advisory CVE-2026-93856
- Date: 20 October 2026
- Upstream advisory: https://security.openstack.org/ossa/OSSA-2026-045.html
What is CVE-2026-93856 and how does it affect YAOOK?
CVE-2026-93856 is a vulnerability in OpenStack Cinder which allows an authenticated attacker assigned the “reader” or “member” role to read Cinder messages from projects for which they do not have permissions.
Is my cluster vulnerable?
The following images are vulnerable:
- Cinder images prior to version 2.0.194
- yaook release date to be confirmed
If an affected image is used in your cluster for the cinder-api deployment, the cluster is vulnerable.
The fixed image has been built in a private pipeline which has been published alongside this advisory to prove the image provenance.
WARNING: Cinder Image 2.2.0 and 2.3.0 didn’t contain the patch
Badly at applying the patches for a new CVE the patches added here got dropped.
As you should also rollout the patches for OSSA-2026-052, please update now to cinder tag 2.4.0.
Further information can be found at the bug report:
Upgrading
A new stable release will be published according to the release cycle and hotfix releases will be produced starting now. You can upgrade to that release simply by updating your operators.
If you want to patch Cinder ahead of the next regular YAOOK release, you can set the YAOOK_OP_VERSIONS_OVERRIDE variable in your Cinder operator container to pull the image before the YAOOK comprehensive release is ready.
The best way to do this is to set the following in the `values.yaml` file of your cinder-operator (make sure to merge this correctly with any existing `values.yaml` file, if you have one).
operator:
extraEnv:
- name: YAOOK_OP_VERSIONS_OVERRIDE
value: |
{
"registry.yaook.cloud/yaook/cinder-2024.1": "registry.yaook.cloud/yaook/cinder-2024.1:2.0.194",
"registry.yaook.cloud/yaook/cinder-2024.2": "registry.yaook.cloud/yaook/cinder-2024.2:2.0.194",
"registry.yaook.cloud/yaook/cinder-2025.1": "registry.yaook.cloud/yaook/cinder-2025.1:2.0.194",
"registry.yaook.cloud/yaook/cinder-2025.2": "registry.yaook.cloud/yaook/cinder-2025.2:2.0.194",
"registry.yaook.cloud/yaook/cinder-2026.1": "registry.yaook.cloud/yaook/cinder-2026.1:2.0.194"
}
If you are not using Helm, you can add the environment variable to the `env` section of your Cinder Operator’s Deployment’s pod template.