- Announce - lists.alasca.cloud

[Security Advisory][nova] CVE-2026-46448
by Stefan Hoffmann June 17, 2026

June 17, 2026

Hi yaook users, yesterday OpenStack published a security advisory for nova. Nova’s server create API does not strip internal scheduler hints. An authenticated user can bypass Placement resource claims and scheduling constraint enforcement, including availability zone, host aggregate, and image trait restrictions. The resulting instance has no Placement allocation, which can lead to compute node resource exhaustion and cross-tenant data persistence on NVMe devices after instance deletion. The following images are vulnerable: nova images before 1.1.141 yaook release before 2.3.2 Hints on upgrading are written at our security advisory[1] Best regards Stefan [1] https://yaook.cloud/security-advisories-cve-2026-46448/ -- Stefan Hoffmann DevOps Engineer Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 36 stefan.hoffmann(a)cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann

1 0

[Security Advisory][keystone][neutron] OSSA-2026-007, CVE-2026-49299, CVE-2026-50266
by Stefan Hoffmann June 10, 2026

June 10, 2026

Hi, in the last weeks some further CVEs got published by OpenStack. The patches are mostly already in the upstream branches, we build backports for not supported versions. But our images needed to be rebuild to fetch the new changes. These keystone CVE is a vulnerability in the Keystone LDAP identity backend. When the user_enabled_invert configuration option was False (the default), Keystone did not correctly interpret the LDAP enabled attribute, causing users disabled in LDAP to be treated as enabled and allowed to authenticate. Deployments using the LDAP identity backend without user_enabled_invert=True or user_enabled_emulation are affected. The CVEs in OpenStack Neutron allow bypassing policies for ports or tagging. The following images are vulnerable: * keystone images before 3.0.88 * neutron images before 1.0.191 * yaook release before 2.3.1 If this images are used in your cluster for keystone-api/neutron-api deployment, the cluster is vulnerable. Also check the security advisories for keystone[1] and neutron[2] how to update your deployments. Regards Stefan [1] https://yaook.cloud/security-advisories-ossa-2026-007/ [2] https://yaook.cloud/security-advisories-cve-2026-49299-50266/ -- Stefan Hoffmann DevOps Engineer Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 36 stefan.hoffmann(a)cloudandheat.com |www.cloudandheat.com Green, Open, Efficient. Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann

1 0

[Security Advisory][keystone] CVE-2026-42998, CVE-2026-42999, CVE-2026-42300, CVE-2026-42301, CVE-2026-44394
by Stefan Hoffmann May 28, 2026

May 28, 2026

Hi, OpenStack published a bunsh of CVEs at keystone. These five CVEs in OpenStack Keystone are all post-auth privilege escalation or scope expansion vulnerabilities. All Keystone releases supported by YAOOK are affected. For details of the particular exploitation flows, please consult the upstream advisory. The YAOOK authors consider CVE-2026-42999 to be the most severe one. It allows cross-project privilege escalation by anyone who can obtain a valid OpenStack token, effectively breaking tenant isolation and potentially allowing escalation to cloud admin privileges. The following images are vulnerable: * keystone images before 3.0.87 * yaook release before 2.3.0 If this image is used in your cluster for the keystone-api deployment, the cluster is vulnerable. The fixed image has been built in a private pipeline[1] which has been published alongside this advisory to prove the image provenance. We recommend to *immediately* add a YAOOK_OP_VERSIONS_OVERRIDE[2] variable to your Keystone operator container to pull the image before the YAOOK comprehensive release is ready. |operator: extraEnv: - name: YAOOK_OP_VERSIONS_OVERRIDE value: | { "registry.yaook.cloud/yaook/keystone-2023.2": "registry.yaook.cloud/yaook/keystone-2023.2:3.0.87", "registry.yaook.cloud/yaook/keystone-2024.1": "registry.yaook.cloud/yaook/keystone-2024.1:3.0.87", "registry.yaook.cloud/yaook/keystone-2024.2": "registry.yaook.cloud/yaook/keystone-2024.2:3.0.87", "registry.yaook.cloud/yaook/keystone-2025.1": "registry.yaook.cloud/yaook/keystone-2025.1:3.0.87", "registry.yaook.cloud/yaook/keystone-2025.2": "registry.yaook.cloud/yaook/keystone-2025.2:3.0.87" }| More info can be found in our security advisory[3]. Regards Stefan [1] https://gitlab.com/yaook-security/images/keystone/-/pipelines/2556551510 [2] https://docs.yaook.cloud/user/references/env-reference.html#envvar-YAOOK_OP… [3] https://yaook.cloud/security-advisories-cve-2026-42998-43001-44394/ -- Stefan Hoffmann DevOps Engineer Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 36 stefan.hoffmann(a)cloudandheat.com |www.cloudandheat.com Green, Open, Efficient. Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann

1 0

[Security Advisory][CVE-2026-42301] Unrestricted application credential can cross project boundaries
by Stefan Hoffmann May 27, 2026

May 27, 2026

Hi yaook users, OpenStack published a Bug for keystone[1]. CVE-2026-42301 allows an attacker who gets hold of an unrestricted application credential to cross project boundaries to another project, if that project is accessible to the user who created the application credential. Thus, the project scoping of application credentials is broken. Also check our Security Advisory[2]. The following images are vulnerable: – keystone images before 3.0.86 – yaook release before 2.2.1 (<= 2.2.0) If this image is used in your cluster for the keystone-api deployment, the cluster is vulnerable. A new stable release will be published according to the release cycle. You can upgrade to that release simply by updating your operators. If you want to upgrade in advance you can pin your keystone image to 3.0.86 in the keystone-operator (adjust the OpenStack version to the version you have deployed): |values: operator: extraEnv: - name: YAOOK_OP_VERSIONS_OVERRIDE value: | || { "registry.yaook.cloud/yaook/keystone-2023.2": "registry.yaook.cloud/yaook/keystone-2023.2:3.0.86", "registry.yaook.cloud/yaook/keystone-2024.1": "registry.yaook.cloud/yaook/keystone-2024.1:3.0.86", "registry.yaook.cloud/yaook/keystone-2024.2": "registry.yaook.cloud/yaook/keystone-2024.2:3.0.86", "registry.yaook.cloud/yaook/keystone-2025.1": "registry.yaook.cloud/yaook/keystone-2025.1:3.0.86", "registry.yaook.cloud/yaook/keystone-2025.2": "registry.yaook.cloud/yaook/keystone-2025.2:3.0.86" }| Best regards Stefan [1] https://bugs.launchpad.net/keystone/+bug/2149775 [2] https://yaook.cloud/security-advisories-cve-2026-42301/ -- Stefan Hoffmann DevOps Engineer Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 36 stefan.hoffmann(a)cloudandheat.com |www.cloudandheat.com Green, Open, Efficient. Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann

1 0

YAOOK Security Advisory for OVN CVE-2026-5265 and CVE-2026-5367
by Stefan Hoffmann May 26, 2026

May 26, 2026

Hi yaook users, OVN has two CVEs that allows a user to read data from memory/packages they are not allowed to read. See also the advisory[1]. The following images are vulnerable: ovn images before 1.0.153 yaook release before v2.2.0 and the version v2.2.0 If any of these images are used in your cluster, the cluster is vulnerable. A new stable release will be published according to the release cycle. You can upgrade to that release simply by updating your operators. If you want to upgrade in advance you can pin your ovn image to v24.09.3-1.0.153 in the neutron-operator (adjust the OpenStack version to the version you have deployed): |values: operator: extraEnv: - name: YAOOK_OP_VERSIONS_OVERRIDE value: | registry.yaook.cloud/yaook/ovn: registry.yaook.cloud/yaook/ovn:v24.09.3-1.0.153| Regards Stefan [1] https://yaook.cloud/security-advisories-cve-2026-5265-5367/ -- Stefan Hoffmann DevOps Engineer Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 36 stefan.hoffmann(a)cloudandheat.com |www.cloudandheat.com Green, Open, Efficient. Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann

1 0

[Security Advisory][CVE-2026-33551] Restricted application credentials can create EC2 credentials
by Stefan Hoffmann April 8, 2026

April 8, 2026

Hi, yesterday OpenStack published a security advisory for keystone. The vulnerability is at Keystone’s EC2 credential creation endpoint. By using a restricted application credential to call the EC2 credential creation API, an authenticated user with only a reader role may obtain an EC2/S3 credential that carries the full set of the parent user’s S3 permissions, effectively bypassing the role restrictions imposed on the application credential. Only deployments that use restricted application credentials in combination with the EC2/S3 compatibility API (swift3 / s3api) are affected. keystone version 3.0.81 has the fixed version. With yaook release 1.4.2 and 2.0.1 this will be also fixed in the pinned_versions of the operators. (still in building) You can patch your keystone with this version pin: values: operator: extraEnv: - name: YAOOK_OP_VERSIONS_OVERRIDE value: | registry.yaook.cloud/yaook/keystone-2025.1: registry.yaook.cloud/yaook/keystone-2025.1:3.0.81 Also see our advisory: https://yaook.cloud/security-advisories-cve-2026-33551 Best regards Stefan -- Stefan Hoffmann DevOps-Engineer Cloud&Heat Cloud&Heat Technologies GmbH Königsbrücker Straße 96 (Halle 15) | 01099 Dresden +49 351 479 367 36 stefan.hoffmann(a)cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. [1] Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann [1] Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. https://www.cloudandheat.com/

1 0

[Yaook] [CVE][OSSA-2026-004] Server-Side Request Forgery (SSRF) vulnerabilities in OpenStack Glance image import functionality
by Stefan Hoffmann March 20, 2026

March 20, 2026

I forgot to send the advisory also here, but I guess, for now, this list is not used by many. Hi yaook and OpenStack Users, today a new security advisory was published by OpenStack and yaook now has a fix for it. Server-Side Request Forgery (SSRF) vulnerabilities in OpenStack Glance image import functionality By use of HTTP redirects, an authenticated user can bypass URL validation checks and redirect to internal services. Only glance image import functionality is affected. In particular, the ‚web-download‘ and ‚glance-download‘ import methods are subject to this vulnerability, as is the optional (not enabled by default) ‚ovf_process‘ image import plugin. The following images are vulnerable: glance images BEFORE 1.1.156 Yaook versions <= v1.4.0 and 1.5.0 If any of these images are used in your cluster, the cluster is vulnerable. A new stable release 1.4.1 will be published today. You can upgrade to that release simply by updating your operators. Release 1.5.1 will also have this fix. If you don’t want to wait for the release, you can use a version override at the glance-operator (adjust the OpenStack version to the version you have deployed): values: operator: extraEnv: - name: YAOOK_OP_VERSIONS_OVERRIDE value: | registry.yaook.cloud/yaook/glance-2025.1: registry.yaook.cloud/yaook/glance-2025.1:1.1.156 See also https://yaook.cloud/security-advisories-ossa-2026-004/ Best regards Stefan

1 0