YAOOK Security Advisory OSSA-2026-052
Date: 2026-11-17
Upstream advisory: https://security.openstack.org/ossa/OSSA-2026-052.html
What is OSSA-2026-052 and how does it affect YAOOK?
OSSA-2026-052 is a vulnerability in keystonemiddleware access rule path matching. By supplying a malicious regular expression when creating an application credential access_rules entry, an authenticated user may consume resources in the consuming process making a service unresponsive. All OpenStack service deployments may be affected.
Is my cluster vulnerable?
The following table contains the affected images, fixed versions as well as links to the pipeline containing the image build with the fixed image.
WARNING: Cinder Image dropped patches for CVE-2026-93856
Badly we need to announce, that the cinder image 2.2.0, we proposed here as fixed version, has the fixes for this CVE but by accident dropped the patches for CVE-2026-93856.
We updated the image, so cinder with Tag 2.4.0 includes all the patches.
Further information can also be found in the bug report.
Thanks to Kris Shannon and Patrick Bartels for reporting this issue and handling the fix.
The table and override below contains the updated image tag.
Image name | Fixed version | Verification pipeline |
barbican | 1.2.0 | |
ceilometer | 1.4.0 | |
cinder | 2.4.0 | |
designate | 1.2.0 | |
glance | 1.3.0 | |
gnocchi | 1.1.0 | |
infra-ironic | 1.1.0 | |
keystone | 3.2.0 | |
neutron | 1.3.0 | |
nova | 1.3.0 | |
octavia | 1.3.0 | |
placement | 2.2.0 |
If an affected image is used in your cluster for the respective API deployments, the cluster is vulnerable.
The YAOOK release 3.8.0 pins the fixed image versions for all services.
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 ahead of the next regular YAOOK release, you can set the YAOOK_OP_VERSIONS_OVERRIDE variable in your respective operator containers 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 of your operators (make sure to merge this correctly with an existing values.yaml, if you have that).
Note: the below snippet contains version overrides for all images. It is safe to apply these to all operators.
operator:extraEnv:- name: YAOOK_OP_VERSIONS_OVERRIDEvalue: |{"registry.yaook.cloud/yaook/barbican-2024.1": "registry.yaook.cloud/yaook/barbican-2024.1:1.2.0","registry.yaook.cloud/yaook/barbican-2024.2": "registry.yaook.cloud/yaook/barbican-2024.2:1.2.0","registry.yaook.cloud/yaook/barbican-2025.1": "registry.yaook.cloud/yaook/barbican-2025.1:1.2.0","registry.yaook.cloud/yaook/barbican-2025.2": "registry.yaook.cloud/yaook/barbican-2025.2:1.2.0","registry.yaook.cloud/yaook/barbican-2026.1": "registry.yaook.cloud/yaook/barbican-2026.1:1.2.0","registry.yaook.cloud/yaook/ceilometer-2024.1": "registry.yaook.cloud/yaook/ceilometer-2024.1:1.4.0","registry.yaook.cloud/yaook/ceilometer-2024.2": "registry.yaook.cloud/yaook/ceilometer-2024.2:1.4.0","registry.yaook.cloud/yaook/ceilometer-2025.1": "registry.yaook.cloud/yaook/ceilometer-2025.1:1.4.0","registry.yaook.cloud/yaook/ceilometer-2025.2": "registry.yaook.cloud/yaook/ceilometer-2025.2:1.4.0","registry.yaook.cloud/yaook/ceilometer-2026.1": "registry.yaook.cloud/yaook/ceilometer-2026.1:1.4.0","registry.yaook.cloud/yaook/cinder-2024.1": "registry.yaook.cloud/yaook/cinder-2024.1:2.4.0","registry.yaook.cloud/yaook/cinder-2024.2": "registry.yaook.cloud/yaook/cinder-2024.2:2.4.0","registry.yaook.cloud/yaook/cinder-2025.1": "registry.yaook.cloud/yaook/cinder-2025.1:2.4.0","registry.yaook.cloud/yaook/cinder-2025.2": "registry.yaook.cloud/yaook/cinder-2025.2:2.4.0","registry.yaook.cloud/yaook/cinder-2026.1": "registry.yaook.cloud/yaook/cinder-2026.1:2.4.0","registry.yaook.cloud/yaook/designate-2024.1": "registry.yaook.cloud/yaook/designate-2024.1:1.2.0","registry.yaook.cloud/yaook/designate-2024.2": "registry.yaook.cloud/yaook/designate-2024.2:1.2.0","registry.yaook.cloud/yaook/designate-2025.1": "registry.yaook.cloud/yaook/designate-2025.1:1.2.0","registry.yaook.cloud/yaook/designate-2025.2": "registry.yaook.cloud/yaook/designate-2025.2:1.2.0","registry.yaook.cloud/yaook/designate-2026.1": "registry.yaook.cloud/yaook/designate-2026.1:1.2.0","registry.yaook.cloud/yaook/glance-2024.1": "registry.yaook.cloud/yaook/glance-2024.1:1.3.0","registry.yaook.cloud/yaook/glance-2024.2": "registry.yaook.cloud/yaook/glance-2024.2:1.3.0","registry.yaook.cloud/yaook/glance-2025.1": "registry.yaook.cloud/yaook/glance-2025.1:1.3.0","registry.yaook.cloud/yaook/glance-2025.2": "registry.yaook.cloud/yaook/glance-2025.2:1.3.0","registry.yaook.cloud/yaook/glance-2026.1": "registry.yaook.cloud/yaook/glance-2026.1:1.3.0","registry.yaook.cloud/yaook/gnocchi-2024.1": "registry.yaook.cloud/yaook/gnocchi-2024.1:1.1.0","registry.yaook.cloud/yaook/gnocchi-2024.2": "registry.yaook.cloud/yaook/gnocchi-2024.2:1.1.0","registry.yaook.cloud/yaook/gnocchi-2025.1": "registry.yaook.cloud/yaook/gnocchi-2025.1:1.1.0","registry.yaook.cloud/yaook/infra-ironic-2024.1": "registry.yaook.cloud/yaook/infra-ironic-2024.1:1.1.0","registry.yaook.cloud/yaook/infra-ironic-2024.2": "registry.yaook.cloud/yaook/infra-ironic-2024.2:1.1.0","registry.yaook.cloud/yaook/infra-ironic-2025.1": "registry.yaook.cloud/yaook/infra-ironic-2025.1:1.1.0","registry.yaook.cloud/yaook/infra-ironic-2025.2": "registry.yaook.cloud/yaook/infra-ironic-2025.2:1.1.0","registry.yaook.cloud/yaook/infra-ironic-2026.1": "registry.yaook.cloud/yaook/infra-ironic-2026.1:1.1.0","registry.yaook.cloud/yaook/keystone-2024.1": "registry.yaook.cloud/yaook/keystone-2024.1:3.2.0","registry.yaook.cloud/yaook/keystone-2024.2": "registry.yaook.cloud/yaook/keystone-2024.2:3.2.0","registry.yaook.cloud/yaook/keystone-2025.1": "registry.yaook.cloud/yaook/keystone-2025.1:3.2.0","registry.yaook.cloud/yaook/keystone-2025.2": "registry.yaook.cloud/yaook/keystone-2025.2:3.2.0","registry.yaook.cloud/yaook/keystone-2026.1": "registry.yaook.cloud/yaook/keystone-2026.1:3.2.0","registry.yaook.cloud/yaook/neutron-2023.2": "registry.yaook.cloud/yaook/neutron-2023.2:1.3.0","registry.yaook.cloud/yaook/neutron-2024.1": "registry.yaook.cloud/yaook/neutron-2024.1:1.3.0","registry.yaook.cloud/yaook/neutron-2024.2": "registry.yaook.cloud/yaook/neutron-2024.2:1.3.0","registry.yaook.cloud/yaook/neutron-2025.1": "registry.yaook.cloud/yaook/neutron-2025.1:1.3.0","registry.yaook.cloud/yaook/neutron-2025.2": "registry.yaook.cloud/yaook/neutron-2025.2:1.3.0","registry.yaook.cloud/yaook/neutron-2026.1": "registry.yaook.cloud/yaook/neutron-2026.1:1.3.0","registry.yaook.cloud/yaook/nova-2024.1": "registry.yaook.cloud/yaook/nova-2024.1:1.3.0","registry.yaook.cloud/yaook/nova-2024.2": "registry.yaook.cloud/yaook/nova-2024.2:1.3.0","registry.yaook.cloud/yaook/nova-2025.1": "registry.yaook.cloud/yaook/nova-2025.1:1.3.0","registry.yaook.cloud/yaook/nova-2025.2": "registry.yaook.cloud/yaook/nova-2025.2:1.3.0","registry.yaook.cloud/yaook/nova-2026.1": "registry.yaook.cloud/yaook/nova-2026.1:1.3.0","registry.yaook.cloud/yaook/octavia-2024.1": "registry.yaook.cloud/yaook/octavia-2024.1:1.3.0","registry.yaook.cloud/yaook/octavia-2024.2": "registry.yaook.cloud/yaook/octavia-2024.2:1.3.0","registry.yaook.cloud/yaook/octavia-2025.1": "registry.yaook.cloud/yaook/octavia-2025.1:1.3.0","registry.yaook.cloud/yaook/octavia-2025.2": "registry.yaook.cloud/yaook/octavia-2025.2:1.3.0","registry.yaook.cloud/yaook/octavia-2026.1": "registry.yaook.cloud/yaook/octavia-2026.1:1.3.0","registry.yaook.cloud/yaook/placement-2024.1": "registry.yaook.cloud/yaook/placement-2024.1:2.2.0","registry.yaook.cloud/yaook/placement-2024.2": "registry.yaook.cloud/yaook/placement-2024.2:2.2.0","registry.yaook.cloud/yaook/placement-2025.1": "registry.yaook.cloud/yaook/placement-2025.1:2.2.0","registry.yaook.cloud/yaook/placement-2025.2": "registry.yaook.cloud/yaook/placement-2025.2:2.2.0","registry.yaook.cloud/yaook/placement-2026.1": "registry.yaook.cloud/yaook/placement-2026.1:2.2.0"}
If you are not using Helm, you can add the environment variable to the env section of your operators‘ Deployment’s pod template.
Acknowledgements
- Rock Xu for reporting the vulnerability.
- The OpenStack VMT and in particular Jeremy Stanley for coordinating disclosure.
- Max Stolze Stefan Hoffmann (both with CLOUD&HEAT Technologies GmbH) for reviewing and backporting the patches as well as preparing the patched YAOOK images.