<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenStack Security Advisories — Stackers Network</title>
    <link>https://stackers.network/security/</link>
    <atom:link href="https://stackers.network/security/feed.xml" rel="self" type="application/rss+xml"/>
    <language>en</language>
    <lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0000</lastBuildDate>
    <description>New OpenStack Security Advisories (OSSA) and related CVEs, synced daily from the OpenStack Vulnerability Management Team.</description>
    <item>
      <title>OSSA-2026-052: keystonemiddleware ReDoS in AppCred access_rules processing</title>
      <link>https://stackers.network/security/#OSSA-2026-052</link>
      <guid isPermaLink="false">OSSA-2026-052</guid>
      <pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate>
      <description>Rock Xu reported 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.</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-052.html">OSSA-2026-052</a> &middot; Affects: keystonemiddleware</p><p>Rock Xu reported 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.</p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-051: Local Privilege Escalation in Cinder LIO iSCSI driver</title>
      <link>https://stackers.network/security/#OSSA-2026-051</link>
      <guid isPermaLink="false">OSSA-2026-051</guid>
      <pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate>
      <description>Sami Yessou, cloud engineer at switch.ch, reported a vulnerability in Cinder. By making an os-initialize_connection request with an IQN that includes a path traversal as part of the connector's initiator element, an authenticated user with a 'member' role may create or overwrite files in the volume host filesystem. Only cinder-volume hosts using the LIO iSCSI target driver are affected. This targe</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-051.html">OSSA-2026-051</a> &middot; Affects: cinder</p><p>Sami Yessou, cloud engineer at switch.ch, reported a vulnerability
in Cinder.  By making an os-initialize_connection request with an
IQN that includes a path traversal as part of the connector's
initiator element, an authenticated user with a 'member' role may
create or overwrite files in the volume host filesystem.  Only
cinder-volume hosts using the LIO iSCSI target driver are affected.
This target driver is typically used with the LVM volume driver.</p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-050: keystonemiddleware access_rules bypass via X-Service-Token (CVE-2026-115642)</title>
      <link>https://stackers.network/security/#OSSA-2026-050</link>
      <guid isPermaLink="false">OSSA-2026-050</guid>
      <pubDate>Thu, 29 Oct 2026 00:00:00 +0000</pubDate>
      <description>Nassim Abbaoui with OVHcloud reported a vulnerability in keystonemiddleware application credential access_rules enforcement. By supplying a custom X-Service-Token header in a request, anyone in posession of an access-restricted application credential may bypass those restrictions resulting in elevation of privileges. Deployments that use application credential access_rules, or that enforce token b</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-050.html">OSSA-2026-050</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-115642">CVE-2026-115642</a> &middot; Affects: keystonemiddleware</p><p>Nassim Abbaoui with OVHcloud reported a vulnerability in keystonemiddleware application credential access_rules enforcement. By supplying a custom X-Service-Token header in a request, anyone in posession of an access-restricted application credential may bypass those restrictions resulting in elevation of privileges. Deployments that use application credential access_rules, or that enforce token binding, are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-10-31">Stackers Network Digest — October 31, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-049: Ironic Conductor DoS via gzip bomb configdrive (CVE-2026-115638)</title>
      <link>https://stackers.network/security/#OSSA-2026-049</link>
      <guid isPermaLink="false">OSSA-2026-049</guid>
      <pubDate>Thu, 29 Oct 2026 00:00:00 +0000</pubDate>
      <description>Jay Faulkner of G-Research Open Source Software reported a vulnerability in the Ironic conductor. The Ironic conductor can be subjected to an out of memory or disk full condition when attempting to extract a base64-encoded, gzipped configdrive image submitted via ``/v1/nodes/{node_ident}/states/provision`` when deploying a node. This issue impacts environments where users have access to deploy ins</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-049.html">OSSA-2026-049</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-115638">CVE-2026-115638</a> &middot; Affects: ironic</p><p>Jay Faulkner of G-Research Open Source Software reported a vulnerability
in the Ironic conductor. The Ironic conductor can be subjected to an out
of memory or disk full condition when attempting to extract a
base64-encoded, gzipped configdrive image submitted via
<code translate="no">/v1/nodes/{node_ident}/states/provision</code> when deploying a node.</p>
<p>This issue impacts environments where users have access to deploy
instances directly via Ironic.</p><p>Covered in: <a href="https://stackers.network/issues/2026-10-31">Stackers Network Digest — October 31, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-048: Ironic allows generic node update for maintenance setting (CVE-2026-89419)</title>
      <link>https://stackers.network/security/#OSSA-2026-048</link>
      <guid isPermaLink="false">OSSA-2026-048</guid>
      <pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate>
      <description>The Metal3.io Security team reported a vulnerability in Ironic's API. When calling the Node maintenance API at ``/v1/nodes/{ident}/maintenance``, Ironic properly applies the ``baremetal:node:set_maintenance`` and ``baremetal:node:clear_maintenance`` policies. However, if a user instead calls the more generic Node update API by sending an HTTP PATCH to ``/v1/nodes/{ident}``, and includes ``maintena</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-048.html">OSSA-2026-048</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-89419">CVE-2026-89419</a> &middot; Affects: ironic</p><p>The Metal3.io Security team reported a vulnerability in Ironic's API.
When calling the Node maintenance API at
<code translate="no">/v1/nodes/{ident}/maintenance</code>, Ironic properly applies the
<code translate="no">baremetal:node:set_maintenance</code> and
<code translate="no">baremetal:node:clear_maintenance</code> policies.</p>
<p>However, if a user instead calls the more generic Node update API by
sending an HTTP PATCH to <code translate="no">/v1/nodes/{ident}</code>, and includes
<code translate="no">maintenance</code> or <code translate="no">maintenance_reason</code> in the dictionary, they can
instead trigger the <code translate="no">baremetal:node:update</code> policy. This may lead to
users unexpectedly having access to change the maintenance setting on
a node.</p>
<p>For clouds using default Ironic policy, this means someone with the
member role on the project indicated in <code translate="no">node.lessee</code> can change
maintenance on the node. This is typically restricted only to accounts
with manager or admin roles on lessee accounts. There is no change in
effective default permissions in the case of <code translate="no">node.owner</code> project
members or system-scoped users.</p><p>Covered in: <a href="https://stackers.network/issues/2026-10-24">Stackers Network Digest — October 24, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-047: Redfish vendor_passthru method allows path injection via ID (CVE-2026-90458)</title>
      <link>https://stackers.network/security/#OSSA-2026-047</link>
      <guid isPermaLink="false">OSSA-2026-047</guid>
      <pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate>
      <description>The Metal3.io Security team reported a vulnerability in Ironic's API. When calling the ``vendor_passthru`` API endpoint provided by the ``redfish`` management interface to create or delete a subscription, a malicious System-scoped Administrator could instead perform an HTTP DELETE or HTTP GET on an arbitrary path on a node's BMC. In a worst case scenario, this could lead to user accounts being del</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-047.html">OSSA-2026-047</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-90458">CVE-2026-90458</a> &middot; Affects: ironic</p><p>The Metal3.io Security team reported a vulnerability in Ironic's API.
When calling the <code translate="no">vendor_passthru</code> API endpoint provided by the
<code translate="no">redfish</code> management interface to create or delete a subscription,
a malicious System-scoped Administrator could instead perform an HTTP
DELETE or HTTP GET on an arbitrary path on a node's BMC. In a worst
case scenario, this could lead to user accounts being deleted from
the Redfish service on the BMC.</p>
<p>Only clouds with nodes enrolled in a redfish hardware type are
susceptible to this vulnerability.</p><p>Covered in: <a href="https://stackers.network/issues/2026-10-24">Stackers Network Digest — October 24, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-046: Manila allows cross-project public-share and export-metadata changes (CVE-2026-71195)</title>
      <link>https://stackers.network/security/#OSSA-2026-046</link>
      <guid isPermaLink="false">OSSA-2026-046</guid>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      <description>Chen YuXiang from the Institute of Computing Technology, Chinese Academy of Sciences reported that a non-owner could modify access rules and export-location metadata of another project's public share. Goutham Pacha Ravi and Carlos da Silva from Red Hat identified further public-share paths: a non-owner could soft-delete or restore a foreign public share, or create a backup of it. A compatible stor</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-046.html">OSSA-2026-046</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-71195">CVE-2026-71195</a> &middot; Affects: manila</p><p>Chen YuXiang from the Institute of Computing Technology, Chinese Academy of
Sciences reported that a non-owner could modify access rules and
export-location metadata of another project's public share. Goutham Pacha
Ravi and Carlos da Silva from Red Hat identified further public-share paths:
a non-owner could soft-delete or restore a foreign public share, or create a
backup of it. A compatible storage backend may apply unauthorized changes to
existing access rules, disrupting access for the share's owner or authorized
users.</p>
<p>Separately, Yuliang Xiao reported that the export-location metadata API does
not scope its lookup to the share in the request. An authenticated project
member may therefore read, modify, or delete another project's export-location
metadata by supplying the target export-location UUID with the identifier of
a share they control. This issue is more easily exploitable with public
shares.</p>
<p>Deployments with public shares are affected by the public-share operations.
Deployments that utilize export-location metadata for shares are affected by the metadata vulnerability.</p><p>Covered in: <a href="https://stackers.network/issues/2026-10-24">Stackers Network Digest — October 24, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-045: Cross-project information disclosure in Cinder Messages API (CVE-2026-93856)</title>
      <link>https://stackers.network/security/#OSSA-2026-045</link>
      <guid isPermaLink="false">OSSA-2026-045</guid>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      <description>Yuliang Xiao, an independent reporter, and Chen YuXiang of the Institute of Computing Technology, Chinese Academy of Sciences independently reported a vulnerability in Cinder's messages API. A non-admin user with the project-scoped 'member' or 'reader' role making the Block Storage API v3.3 &quot;List messages&quot; call finds the non-expired user messages for other projects included in the response, result</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-045.html">OSSA-2026-045</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-93856">CVE-2026-93856</a> &middot; Affects: cinder</p><p>Yuliang Xiao, an independent reporter, and Chen YuXiang of the
Institute of Computing Technology, Chinese Academy of Sciences independently
reported a vulnerability in Cinder's messages API. A non-admin user
with the project-scoped 'member' or 'reader' role making the Block
Storage API v3.3 "List messages" call finds the non-expired user
messages for other projects included in the response, resulting in
the leakage of UUIDs of resources owned by other projects in addition
to the user message about the other projects' resources (which, by
design, are sanitized generic messages). All Cinder deployments are
affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-10-24">Stackers Network Digest — October 24, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-044: Four authorization and privilege vulnerabilities in Mistral (CVE-2026-93858, CVE-2026-93860, CVE-2026-93861, CVE-2026-97147)</title>
      <link>https://stackers.network/security/#OSSA-2026-044</link>
      <guid isPermaLink="false">OSSA-2026-044</guid>
      <pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate>
      <description>Arnaud Morin from OVHcloud reported that several of Mistral's v2 API write paths resolve the target object with a query that can return another project's resource, then write to it (CVE-2026-97147). An authenticated project member can use this to rewrite and un-publish another project's public action definitions and environments. A project administrator can create a workbook whose embedded ad-hoc </description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-044.html">OSSA-2026-044</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-93858">CVE-2026-93858</a>, <a href="https://www.cve.org/CVERecord?id=CVE-2026-93860">CVE-2026-93860</a>, <a href="https://www.cve.org/CVERecord?id=CVE-2026-93861">CVE-2026-93861</a>, <a href="https://www.cve.org/CVERecord?id=CVE-2026-97147">CVE-2026-97147</a> &middot; Affects: Mistral</p><p>Arnaud Morin from OVHcloud reported that several of Mistral's v2 API
write paths resolve the target object with a query that can return
another project's resource, then write to it (CVE-2026-97147). An
authenticated project member can use this to rewrite and un-publish
another project's public action definitions and environments. A
project administrator can create a workbook whose embedded ad-hoc
action or workflow name collides with a resource of another project,
which moves that resource into the caller's project and causes the
original owner's subsequent updates of it to fail with server
errors. All deployments exposing the Mistral API are affected.</p>
<p>Chen YuXiang from the Institute of Computing Technology, Chinese
Academy of Sciences reported that Mistral's workflow membership API
lets a project that has accepted a share of another project's
private workflow create a further membership naming a third project
(CVE-2026-93861). The new membership row is created with its
project_id defaulted to the accepting project rather than the
original workflow owner, so the owner can neither see nor delete it.
The third project can accept this membership it was never actually
granted by the owner, then read and execute the owner's private
workflow; only the accepting (not the owning) project can later
revoke that access.</p>
<p>Chen YuXiang also reported a vulnerability in Mistral's ssh_proxied
action provider (CVE-2026-93858). By supplying a specially-crafted
action payload, an unprivileged authenticated user may override
paramiko's proxy_command resulting in execution of arbitrary code on
the executor host operating system. Only Mistral deployments
allowing the std.ssh_proxied action provider (the default) are
affected.</p>
<p>Chen YuXiang further reported a vulnerability in Mistral's
maintenance API method (CVE-2026-93860). By calling the maintenance
API method, an unprivileged authenticated user may pause processing
for creation of new objects for all tenant projects resulting in a
temporary denial of service. All Mistral deployments are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-10-10">Stackers Network Digest — October 10, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-043: Zaqar WebSocket project substitution allows cross-project queue access (CVE-2026-107363)</title>
      <link>https://stackers.network/security/#OSSA-2026-043</link>
      <guid isPermaLink="false">OSSA-2026-043</guid>
      <pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate>
      <description>Chen YuXiang from the Institute of Computing Technology, Chinese Academy of Sciences reported a vulnerability in Zaqar's WebSocket transport. An authenticated remote attacker who knows a target project's UUID may substitute it in subsequent WebSocket frames to enumerate, inspect, create, or delete queues belonging to that project. This may result in unauthorized disclosure, modification, or loss o</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-043.html">OSSA-2026-043</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-107363">CVE-2026-107363</a> &middot; Affects: zaqar</p><p>Chen YuXiang from the Institute of Computing Technology, Chinese Academy
of Sciences reported a vulnerability in Zaqar's WebSocket transport. An
authenticated remote attacker who knows a target project's UUID may
substitute it in subsequent WebSocket frames to enumerate, inspect,
create, or delete queues belonging to that project. This may result in
unauthorized disclosure, modification, or loss of queue data. Only
deployments using the WebSocket transport with Keystone authentication
are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-10-10">Stackers Network Digest — October 10, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-042: Zaqar empty URL-Signature header bypasses authentication (CVE-2026-97404)</title>
      <link>https://stackers.network/security/#OSSA-2026-042</link>
      <guid isPermaLink="false">OSSA-2026-042</guid>
      <pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate>
      <description>pple, an independent security researcher, reported that Zaqar's WSGI transport mishandles an empty URL-Signature header: a request carrying the header with an empty value bypasses both Keystone authentication and pre-signed URL verification. An unauthenticated remote attacker who knows a target project's UUID can then read, enumerate, create, and delete that project's queues, messages, claims, and</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-042.html">OSSA-2026-042</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-97404">CVE-2026-97404</a> &middot; Affects: zaqar</p><p>pple, an independent security researcher, reported that Zaqar's
WSGI transport mishandles an empty URL-Signature header: a request
carrying the header with an empty value bypasses both Keystone
authentication and pre-signed URL verification. An unauthenticated
remote attacker who knows a target project's UUID can then read,
enumerate, create, and delete that project's queues, messages,
claims, and subscriptions. By additionally claiming an
administrative role, the attacker may also perform administrative
operations, such as managing pools and flavors in admin_mode
deployments. Only deployments using the WSGI transport with an
authentication strategy configured are affected; the websocket
transport is not affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-09-26">Stackers Network Digest — September 26, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-041: Cross-container information disclosure via Swift tempurl (CVE-2026-97149)</title>
      <link>https://stackers.network/security/#OSSA-2026-041</link>
      <guid isPermaLink="false">OSSA-2026-041</guid>
      <pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate>
      <description>Oren Yomtov from ACT Security and &quot;swdb&quot;, a security researcher, independently reported a vulnerability in the Swift tempurl middleware. A party holding a single-object PUT TempURL signed with an account-level key (``X-Account-Meta-Temp-URL-Key``) could resend the signed request with an ``X-Copy-From`` header naming any object in the same account, causing Swift to copy the named object into the gr</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-041.html">OSSA-2026-041</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-97149">CVE-2026-97149</a> &middot; Affects: swift</p><p>Oren Yomtov from ACT Security and "swdb", a security
researcher, independently reported a vulnerability in the
Swift tempurl middleware. A party holding a single-object PUT
TempURL signed with an account-level key
(<code translate="no">X-Account-Meta-Temp-URL-Key</code>) could resend the signed request
with an <code translate="no">X-Copy-From</code> header naming any object in the same
account, causing Swift to copy the named object into the granted
destination object, and read the copied bytes back with a second
GET TempURL, disclosing objects the holder of the TempURL was not
authorized to access. Only deployments with the tempurl middleware
enabled are affected. The copy is limited to the account that
owns the key, and the attacker must know the target container and
object name.</p>
<p>As a mitigation, operators can add <code translate="no">x-copy-from</code> to the
<code translate="no">incoming_remove_headers</code> option of the <code translate="no">[filter:tempurl]</code>
section of their proxy server configuration. With that
configuration the header is silently removed and the PUT stores no
data; the patches below instead reject the request with a 400
response.</p><p>Covered in: <a href="https://stackers.network/issues/2026-09-26">Stackers Network Digest — September 26, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-040: Multiple authorization vulnerabilities in the Blazar V2 lease API (CVE-2026-93852, CVE-2026-93854)</title>
      <link>https://stackers.network/security/#OSSA-2026-040</link>
      <guid isPermaLink="false">OSSA-2026-040</guid>
      <pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate>
      <description>Rohan Das from the University of Engineering and Management, Kolkata, reported that the Blazar V2 lease API does not enforce object-level authorization on its update and delete operations. As a result, any authenticated user who knows a lease ID can modify or delete leases belonging to other users and projects. The same reporter found that the Blazar V2 lease listing operation returns leases for e</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-040.html">OSSA-2026-040</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-93852">CVE-2026-93852</a>, <a href="https://www.cve.org/CVERecord?id=CVE-2026-93854">CVE-2026-93854</a> &middot; Affects: blazar</p><p>Rohan Das from the University of Engineering and Management, Kolkata,
reported that the Blazar V2 lease API does not enforce object-level
authorization on its update and delete operations. As a result, any
authenticated user who knows a lease ID can modify or delete leases
belonging to other users and projects.</p>
<p>The same reporter found that the Blazar V2 lease listing operation
returns leases for every project without enforcing project scoping
or an administrator-only policy. Any authenticated user can
enumerate other projects' leases, exposing lease and reservation
identifiers along with reservation metadata. The exposed
identifiers enable the object-level authorization bypass
described above, allowing an attacker to then modify or delete the
enumerated leases.</p>
<p>Only deployments that enable Blazar's V2 lease API are affected.
Deployers that do not use the V2 API endpoint can set
<code translate="no">api_v2_controllers</code> to an empty value in the <code translate="no">[api]</code> section of
<code translate="no">blazar.conf</code>. Patches below address the issue if the API
controllers cannot be disabled.</p><p>Covered in: <a href="https://stackers.network/issues/2026-09-26">Stackers Network Digest — September 26, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-039: HAProxy configuration injection leading to remote code execution in Octavia (CVE-2026-94572, CVE-2026-94571)</title>
      <link>https://stackers.network/security/#OSSA-2026-039</link>
      <guid isPermaLink="false">OSSA-2026-039</guid>
      <pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate>
      <description>Chen YuXiang from the Institute of Computing Technology, Chinese Academy of Sciences reported input validation flaws in the Octavia load balancer API. The listener and pool ``tls_ciphers`` fields and the L7 policy ``redirect_url`` and ``redirect_prefix`` fields were written into the HAProxy configuration generated on the amphora without rejecting control characters, allowing an authenticated user </description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-039.html">OSSA-2026-039</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-94572">CVE-2026-94572</a>, <a href="https://www.cve.org/CVERecord?id=CVE-2026-94571">CVE-2026-94571</a> &middot; Affects: octavia</p><p>Chen YuXiang from the Institute of Computing Technology, Chinese
Academy of Sciences reported input validation flaws in the Octavia
load balancer API. The listener and pool <code translate="no">tls_ciphers</code> fields and
the L7 policy <code translate="no">redirect_url</code> and <code translate="no">redirect_prefix</code> fields were
written into the HAProxy configuration generated on the amphora
without rejecting control characters, allowing an authenticated user
who owns a load balancer managed by OpenStack Octavia's Amphora
provider to inject arbitrary HAProxy configuration directives.</p>
<p>Subsequently, an independent reporter, "Rolix", demonstrated that
these flaws can be exploited to execute arbitrary commands as root
on the provider-managed amphora, to disclose other tenants' TLS
private keys and certificates and the deployment heartbeat key
stored on the amphora, and to reach the control-plane network to
which the amphora is attached.</p>
<p>Only the Amphora provider driver is affected. Deployments that use a
different provider driver do not render tenant input into an HAProxy
configuration and are not affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-09-26">Stackers Network Digest — September 26, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-038: Multiple SSRF vulnerabilities in Glance web-download and HTTP image APIs (CVE-2026-71196, CVE-2026-71197, CVE-2026-71198)</title>
      <link>https://stackers.network/security/#OSSA-2026-038</link>
      <guid isPermaLink="false">OSSA-2026-038</guid>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0000</pubDate>
      <description>Sergey Kanibor (Luntry), Sami Yessou (switch.ch), and Abhishek Kekane (Red Hat) reported three related SSRF vulnerabilities in OpenStack Glance. The web-download import method ships with insecure default filtering that permits authenticated users to fetch arbitrary internal URLs, including cloud metadata endpoints. The URI validator does not perform DNS resolution before applying host filters, ena</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-038.html">OSSA-2026-038</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-71196">CVE-2026-71196</a>, <a href="https://www.cve.org/CVERecord?id=CVE-2026-71197">CVE-2026-71197</a>, <a href="https://www.cve.org/CVERecord?id=CVE-2026-71198">CVE-2026-71198</a> &middot; Affects: glance</p><p>Sergey Kanibor (Luntry), Sami Yessou (switch.ch), and Abhishek Kekane
(Red Hat) reported three related SSRF vulnerabilities in OpenStack
Glance.</p>
<p>The web-download import method ships with insecure default filtering
that permits authenticated users to fetch arbitrary internal URLs,
including cloud metadata endpoints. The URI validator does not perform
DNS resolution before applying host filters, enabling bypass via
attacker-controlled domains and DNS rebinding attacks. The HTTP image
location API lacks host filtering entirely when the HTTP store is
enabled, and fetched content is stored as image data accessible for
download, converting blind SSRF into full-read exfiltration.</p>
<p>All Glance deployments using the web-download import method or HTTP
image location APIs are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-09-05">Stackers Network Digest — September 05, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-037: Inconsistent scope enforcement for delegated tokens in Keystone (CVE-2026-80182, CVE-2026-80184)</title>
      <link>https://stackers.network/security/#OSSA-2026-037</link>
      <guid isPermaLink="false">OSSA-2026-037</guid>
      <pubDate>Tue, 25 Aug 2026 00:00:00 +0000</pubDate>
      <description>Grzegorz Grasza (Red Hat) reported that OpenStack Keystone did not consistently block delegated tokens from creating new long-lived credentials or authorizing new delegations. Tim Shephard (roiai.ca) separately reported that delegated tokens could be submitted to the token-method authentication path to escape their project scope. A token scoped through an OAuth1 access token, an application creden</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-037.html">OSSA-2026-037</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-80182">CVE-2026-80182</a>, <a href="https://www.cve.org/CVERecord?id=CVE-2026-80184">CVE-2026-80184</a> &middot; Affects: keystone</p><p>Grzegorz Grasza (Red Hat) reported that OpenStack Keystone did not
consistently block delegated tokens from creating new long-lived
credentials or authorizing new delegations. Tim Shephard (roiai.ca)
separately reported that delegated tokens could be submitted to the
token-method authentication path to escape their project scope.</p>
<p>A token scoped through an OAuth1 access token, an application
credential, or a trust could create new long-lived credentials or
authorize new delegations that persist independently of, and outlive,
the credential used to obtain them. Separately, tokens obtained
through any of these delegation mechanisms could be submitted to the
token-method authentication path for reauthentication. When an
application credential token was presented with no explicit scope,
Keystone would issue a new token scoped to the credential owner's
default project rather than the project for which the credential was
issued, escaping the intended project boundary.</p>
<p>All Keystone deployments that permit delegated authentication through
OAuth1 access tokens, application credentials, or trusts are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-09-19">Stackers Network Digest — September 19, 2026</a>, <a href="https://stackers.network/issues/2026-08-29">Stackers Network Digest — August 29, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-036: Aodh cross-project alarm enumeration and Watcher webhook authorization bypass (CVE-2026-76878)</title>
      <link>https://stackers.network/security/#OSSA-2026-036</link>
      <guid isPermaLink="false">OSSA-2026-036</guid>
      <pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
      <description>Chen YuXiang of the Institute of Computing Technology, Chinese Academy of Sciences reported that OpenStack Aodh does not enforce project scope on the alarm listing API when the ``all_projects`` query parameter is supplied with a false value. A non-admin user holding only the reader role can list alarms belonging to other projects, optionally targeting a specific project, exposing alarm metadata su</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-036.html">OSSA-2026-036</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-76878">CVE-2026-76878</a> &middot; Affects: aodh, watcher</p><p>Chen YuXiang of the Institute of Computing Technology, Chinese
Academy of Sciences reported that OpenStack Aodh does not enforce
project scope on the alarm listing API when the <code translate="no">all_projects</code>
query parameter is supplied with a false value. A non-admin user
holding only the reader role can list alarms belonging to other
projects, optionally targeting a specific project, exposing alarm
metadata such as webhook action URLs, signal endpoints, and project
identifiers. All Aodh deployments are affected.</p>
<p>The same reporter found that OpenStack Watcher does not apply
authorization to its webhook trigger endpoint. Any authenticated
user who learns an audit's webhook URL, for example from the Aodh
alarm metadata leaked above, can start an <code translate="no">EVENT</code> audit and its
associated action plan regardless of their own project or role.
All Watcher deployments are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-08-22">Stackers Network Digest — August 22, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-035: Unauthorized QoS policy deletion lock (CVE-2026-74248)</title>
      <link>https://stackers.network/security/#OSSA-2026-035</link>
      <guid isPermaLink="false">OSSA-2026-035</guid>
      <pubDate>Thu, 13 Aug 2026 00:00:00 +0000</pubDate>
      <description>Chen YuXiang with the Institute of Computing Technology, Chinese Academy of Sciences, reported a vulnerability in Octavia quality of service (QoS) policy authorization. By associating another project's QoS policy with an amphora, an authenticated user may prevent deletion of that policy. All Octavia deployments are affected.</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-035.html">OSSA-2026-035</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-74248">CVE-2026-74248</a> &middot; Affects: Octavia</p><p>Chen YuXiang with the Institute of Computing Technology, Chinese Academy of Sciences, reported a vulnerability in Octavia quality of service (QoS) policy authorization. By associating another project's QoS policy with an amphora, an authenticated user may prevent deletion of that policy. All Octavia deployments are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-08-22">Stackers Network Digest — August 22, 2026</a>, <a href="https://stackers.network/issues/2026-08-15">Stackers Network Digest — August 15, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-034: Cross-tenant DNS zone overlap and mDNS DoS via pool scheduling (CVE-2026-71193, CVE-2026-71194)</title>
      <link>https://stackers.network/security/#OSSA-2026-034</link>
      <guid isPermaLink="false">OSSA-2026-034</guid>
      <pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate>
      <description>Tore Anderson of Redpill Linpro AS reported that OpenStack Designate does not enforce cross-pool zone ownership checks when scheduling a zone to a non-default pool via the attribute filter. A tenant can create a sub-zone, super-zone, or duplicate of another tenant's zone by targeting a different pool, enabling DNS hijack or denial of service. Independently, Omer Schwartz of Red Hat identified that</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-034.html">OSSA-2026-034</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-71193">CVE-2026-71193</a>, <a href="https://www.cve.org/CVERecord?id=CVE-2026-71194">CVE-2026-71194</a> &middot; Affects: designate</p><p>Tore Anderson of Redpill Linpro AS reported that OpenStack Designate does not enforce cross-pool zone ownership checks when scheduling a zone to a non-default pool via the attribute filter. A tenant can create a sub-zone, super-zone, or duplicate of another tenant's zone by targeting a different pool, enabling DNS hijack or denial of service. Independently, Omer Schwartz of Red Hat identified that the mDNS handler performs pool-blind record lookups, causing a deterministic denial of service when colliding zones exist across pools. All deployments using multiple Designate pools are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-08-15">Stackers Network Digest — August 15, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-033: Portgroup shard filter bypasses project scope (CVE-2026-71201)</title>
      <link>https://stackers.network/security/#OSSA-2026-033</link>
      <guid isPermaLink="false">OSSA-2026-033</guid>
      <pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate>
      <description>Chen YuXiang of Institute of Computing Technology, Chinese Academy of Sciences reported an issue in Ironic's API. When a project reader requests a list of portgroups filtered by shard, all portgroups in that shard are returned, not just those in their project. This is a similar vulnerability to the one originally advisoried in OSSA-2026-026 -- that issue impacted ports; this impacts portgroups.</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-033.html">OSSA-2026-033</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-71201">CVE-2026-71201</a> &middot; Affects: ironic</p><p>Chen YuXiang of Institute of Computing Technology, Chinese Academy
of Sciences reported an issue in Ironic's API. When a project
reader requests a list of portgroups filtered by shard, all portgroups
in that shard are returned, not just those in their project.</p>
<p>This is a similar vulnerability to the one originally advisoried in
OSSA-2026-026 -- that issue impacted ports; this impacts
portgroups.</p><p>Covered in: <a href="https://stackers.network/issues/2026-08-08">Stackers Network Digest — August 08, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-032: Subnetpool onboarding cross-project subnet mutation (CVE-2026-55707)</title>
      <link>https://stackers.network/security/#OSSA-2026-032</link>
      <guid isPermaLink="false">OSSA-2026-032</guid>
      <pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate>
      <description>Tim Shephard from roiai.ca reported a vulnerability in Neutron's subnetpool onboarding API. A project member can onboard subnets from another project's shared network into their own subnetpool, mutating the victim's persistent subnet state and altering L3 routing, NAT, and address-scope behavior for victim routers. Only deployments with shared or RBAC-shared networks and the subnetpool onboarding </description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-032.html">OSSA-2026-032</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-55707">CVE-2026-55707</a> &middot; Affects: neutron</p><p>Tim Shephard from roiai.ca reported a vulnerability in Neutron's subnetpool onboarding API. A project member can onboard subnets from another project's shared network into their own subnetpool, mutating the victim's persistent subnet state and altering L3 routing, NAT, and address-scope behavior for victim routers. Only deployments with shared or RBAC-shared networks and the subnetpool onboarding extension enabled are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-08-01">Stackers Network Digest — August 01, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-031: Swift proxy denial of service via Accept header (CVE-2026-71190)</title>
      <link>https://stackers.network/security/#OSSA-2026-031</link>
      <guid isPermaLink="false">OSSA-2026-031</guid>
      <pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate>
      <description>Christian Schwede from NVIDIA reported a denial of service vulnerability in Swift's proxy server. The Accept header parser is vulnerable to catastrophic regular expression backtracking. An unauthenticated attacker can send crafted requests that exhaust proxy worker threads, rendering the service unavailable. All deployments running Swift proxy with versions between 1.9.1 and the fixed releases lis</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-031.html">OSSA-2026-031</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-71190">CVE-2026-71190</a> &middot; Affects: swift</p><p>Christian Schwede from NVIDIA reported a denial of service vulnerability in Swift's proxy server. The Accept header parser is vulnerable to catastrophic regular expression backtracking. An unauthenticated attacker can send crafted requests that exhaust proxy worker threads, rendering the service unavailable. All deployments running Swift proxy with versions between 1.9.1 and the fixed releases listed below are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-08-08">Stackers Network Digest — August 08, 2026</a>, <a href="https://stackers.network/issues/2026-08-01">Stackers Network Digest — August 01, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-030: Swift S3API header authorization bypass (CVE-2026-71191, CVE-2026-71192)</title>
      <link>https://stackers.network/security/#OSSA-2026-030</link>
      <guid isPermaLink="false">OSSA-2026-030</guid>
      <pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate>
      <description>Christian Schwede from NVIDIA reported two authorization bypass vulnerabilities in Swift's S3API middleware. Insufficient validation of request headers allows an attacker to copy and read objects belonging to other tenants. The first issue affects the default ``s3_acl=false`` configuration; the second affects deployments with ``s3_acl=true``. Both require the attacker to know the target container </description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-030.html">OSSA-2026-030</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-71191">CVE-2026-71191</a>, <a href="https://www.cve.org/CVERecord?id=CVE-2026-71192">CVE-2026-71192</a> &middot; Affects: swift</p><p>Christian Schwede from NVIDIA reported two authorization bypass vulnerabilities in Swift's S3API middleware. Insufficient validation of request headers allows an attacker to copy and read objects belonging to other tenants. The first issue affects the default <code translate="no">s3_acl=false</code> configuration; the second affects deployments with <code translate="no">s3_acl=true</code>. Both require the attacker to know the target container and object names. All deployments using the S3API middleware with versions between 2.18.0 and the fixed releases listed below are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-08-08">Stackers Network Digest — August 08, 2026</a>, <a href="https://stackers.network/issues/2026-08-01">Stackers Network Digest — August 01, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-029: Zaqar EXTRA-SPEC header bypasses Keystone authentication (CVE-2026-66139)</title>
      <link>https://stackers.network/security/#OSSA-2026-029</link>
      <guid isPermaLink="false">OSSA-2026-029</guid>
      <pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate>
      <description>Chen YuXiang from the Institute of Computing Technology, Chinese Academy of Sciences reported that the Zaqar messaging service bypasses Keystone authentication when an EXTRA-SPEC header is present in the request. An unauthenticated attacker who knows a project UUID can read, enumerate, create, and delete that project's queues without a Keystone token. The EXTRA-SPEC header was intended to support </description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-029.html">OSSA-2026-029</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-66139">CVE-2026-66139</a> &middot; Affects: zaqar</p><p>Chen YuXiang from the Institute of Computing Technology, Chinese Academy of Sciences reported that the Zaqar messaging service bypasses Keystone authentication when an EXTRA-SPEC header is present in the request. An unauthenticated attacker who knows a project UUID can read, enumerate, create, and delete that project's queues without a Keystone token. The EXTRA-SPEC header was intended to support an alternative authentication mechanism, but the backend validation was never implemented, resulting in a complete authentication bypass. All deployments running Zaqar 12.0.0 or later are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-07-25">Stackers Network Digest — July 25, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-028: Credential extraction from Ironic Python Agent via malicious container (CVE-2026-54422)</title>
      <link>https://stackers.network/security/#OSSA-2026-028</link>
      <guid isPermaLink="false">OSSA-2026-028</guid>
      <pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate>
      <description>Yuliang Xiao reported a vulnerability in Ironic Python Agent's bootc container deployment support. A malicious container can extract the secrets used to fetch from the OCI registry on deployment. Operators can fix this issue by applying the provided patches or completely disabling the bootc deploy_interface on their Ironic conductors. Any Ironic user with the ability to deploy arbitrary containers</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-028.html">OSSA-2026-028</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-54422">CVE-2026-54422</a> &middot; Affects: ironic-python-agent</p><p>Yuliang Xiao reported a vulnerability in Ironic Python Agent's bootc container deployment support. A malicious container can extract the secrets used to fetch from the OCI registry on deployment.
Operators can fix this issue by applying the provided patches or completely disabling the bootc deploy_interface on their Ironic conductors.
Any Ironic user with the ability to deploy arbitrary containers from the bootc deploy_interface can exploit this.</p><p>Covered in: <a href="https://stackers.network/issues/2026-07-25">Stackers Network Digest — July 25, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-027: Command execution via unsanitized config (CVE-2026-66138)</title>
      <link>https://stackers.network/security/#OSSA-2026-027</link>
      <guid isPermaLink="false">OSSA-2026-027</guid>
      <pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate>
      <description>Dmitry Tantsur (Red Hat) and Tuomo Tanskanen (Ericsson Software Technology) from the Metal3.io Security Team reported a vulnerability in Ironic-Python-Agent's (IPAs) time syncing code. The value of the ntp_server configuration option is inserted into a shell command without sanitization. This command is run as root very early in the IPA startup flow, allowing an attacker to run arbitrary commands </description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-027.html">OSSA-2026-027</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-66138">CVE-2026-66138</a> &middot; Affects: ironic-python-agent</p><p>Dmitry Tantsur (Red Hat) and Tuomo Tanskanen (Ericsson Software Technology)
from the Metal3.io Security Team reported a vulnerability in
Ironic-Python-Agent's (IPAs) time syncing code.</p>
<p>The value of the ntp_server configuration option is inserted into a shell
command without sanitization. This command is run as root very early in the
IPA startup flow, allowing an attacker to run arbitrary commands as root.</p>
<p>This value can be set in three ways; directly in an operator-created ramdisk,
set via kernel command line using Ironic, or passing the parameters via mDNS
responder for mDNS enabled installation. For the most common, and highest
security risk case, this means a Manager role associated with the project set
as <code translate="no">node.owner</code> may be able to trigger this vulnerability.</p><p>Covered in: <a href="https://stackers.network/issues/2026-07-25">Stackers Network Digest — July 25, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-026: Insufficient Access Controls in Ironic regarding Parent/Child Nodes (CVE-2026-44918)</title>
      <link>https://stackers.network/security/#OSSA-2026-026</link>
      <guid isPermaLink="false">OSSA-2026-026</guid>
      <pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate>
      <description>Dmitry Tantsur (Red Hat) and Tuomo Tanskanen (Ericsson Software Technology) from the Metal3.io Security Team reported a vulnerability in Ironic's access control code. This OSSA represents multiple related vulnerabilities in Ironic RBAC. An authenticated project manager can change the node associated with Volume Connectors or Volume Target objects, potentially changing the project permitted to acce</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-026.html">OSSA-2026-026</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-44918">CVE-2026-44918</a> &middot; Affects: ironic</p><p>Dmitry Tantsur (Red Hat) and Tuomo Tanskanen (Ericsson Software Technology)
from the Metal3.io Security Team reported a vulnerability in Ironic's
access control code.</p>
<p>This OSSA represents multiple related vulnerabilities in Ironic RBAC. An
authenticated project manager can change the node associated with
Volume Connectors or Volume Target objects, potentially changing the
project permitted to access the object. Volume Connectors
contain secrets in environments configuring boot from volume with iSCSI
volumes. This is tracked as bug #2150256.</p>
<p>Objects reparented in this manner cannot be detected
via inspection of the data. Operators who are concerned they may have
had this occur are encouraged to perform a basic audit of node
configuration, for instance, insuring the expected number of
volume targets, and volume connectors are present.</p>
<p>Additionally, a project manager with the ability to create nodes can use
the UUID of a node not owned by their project as a parent node when creating
a new node. This mismatched child node can then be used to impact operations
on the parent, such as forcing it to power on. This is tracked as bug</p>
<h1 id="2150450">2150450.</h1>
<p>Ironic now specifically checks, and requires node parents and children to
have matching <code translate="no">node.owner</code> values. This patch contains an enhancement
to Ironic's upgrade check to detect this mismatched state. Operators can
use the provided <code translate="no">ironic-status upgrade check</code> to identify misconfigured
nodes.</p><p>Covered in: <a href="https://stackers.network/issues/2026-08-08">Stackers Network Digest — August 08, 2026</a>, <a href="https://stackers.network/issues/2026-07-11">Stackers Network Digest — July 11, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-025: RBAC Bypass in IPMI Raw Command Execution (CVE-2026-54423)</title>
      <link>https://stackers.network/security/#OSSA-2026-025</link>
      <guid isPermaLink="false">OSSA-2026-025</guid>
      <pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate>
      <description>Dmitry Tantsur (Red Hat) and Tuomo Tanskanen (Ericsson Software Technology) of the Metal3.io Security Team descovered a vulnerability around IPMI management_interface. A malicious user with access to deploy a node directly via Ironic can specify the IPMI `send_raw` deployment step with a malicious payload and send commands to that nodes' BMC. IPMI `send_raw` capability is exposed multiple ways, in</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-025.html">OSSA-2026-025</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-54423">CVE-2026-54423</a> &middot; Affects: ironic</p><p>Dmitry Tantsur (Red Hat) and Tuomo Tanskanen (Ericsson Software Technology) of the Metal3.io Security Team descovered a vulnerability around IPMI management_interface. A malicious user with access to deploy a node directly via Ironic can specify the IPMI <code translate="no">send_raw</code> deployment step with a malicious payload and send commands to that nodes' BMC.
IPMI <code translate="no">send_raw</code> capability is exposed multiple ways, including via our VendorPassthru interfaces (restricted to system admin) and other step based flows such as cleaning or servicing. This also means any malicious user with the ability to initate manual cleaning and servicing flows with arbitrary steps can also execute this vulnerability.
Operators can fix this issue by applying the provided patches which apply a blocklist forbidding use of the IPMI send_raw functionality in certain provisioning methods. Clouds currently using IPMI send_raw functionality should carefully review the behavior changes in the provided patches to ensure their workflows are not broken.</p><p>Covered in: <a href="https://stackers.network/issues/2026-07-11">Stackers Network Digest — July 11, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>OSSA-2026-024: Swift proxy-server SSRF via header injection (CVE-2026-50221)</title>
      <link>https://stackers.network/security/#OSSA-2026-024</link>
      <guid isPermaLink="false">OSSA-2026-024</guid>
      <pubDate>Tue, 23 Jun 2026 00:00:00 +0000</pubDate>
      <description>Tim Shephard from roiai.ca reported a server-side request forgery (SSRF) vulnerability in Swift's proxy-server. An authenticated user can cause Swift object servers to issue outbound HTTP requests to attacker-specified hosts, potentially exposing internal infrastructure details. All deployments running Swift 2.0.0 or later are affected.</description>
      <content:encoded><![CDATA[<p><a href="https://security.openstack.org/ossa/OSSA-2026-024.html">OSSA-2026-024</a> &middot; <a href="https://www.cve.org/CVERecord?id=CVE-2026-50221">CVE-2026-50221</a> &middot; Affects: swift</p><p>Tim Shephard from roiai.ca reported a server-side request forgery (SSRF) vulnerability in Swift's proxy-server. An authenticated user can cause Swift object servers to issue outbound HTTP requests to attacker-specified hosts, potentially exposing internal infrastructure details. All deployments running Swift 2.0.0 or later are affected.</p><p>Covered in: <a href="https://stackers.network/issues/2026-06-27">Stackers Network Digest — June 27, 2026</a></p>]]></content:encoded>
    </item>
    <item>
      <title>CVE-2026-55748: [OSSN-0097 Errata 1] Horizon RC file escaping (CVE-2026-55748). The previously published Horizon RC-file generation issue now has a CVE assigned. (note)</title>
      <link>https://stackers.network/security/#CVE-2026-55748</link>
      <guid isPermaLink="false">CVE-2026-55748</guid>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <description>[OSSN-0097 Errata 1] Horizon RC file escaping (CVE-2026-55748). The previously published Horizon RC-file generation issue now has a CVE assigned. (note)</description>
      <content:encoded><![CDATA[<p><a href="https://www.cve.org/CVERecord?id=CVE-2026-55748">CVE-2026-55748</a></p><p>Covered in: <a href="https://stackers.network/issues/2026-06-20">Stackers Network Digest — June 20, 2026</a></p>]]></content:encoded>
    </item>
  </channel>
</rss>
