<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 16 Nov 2026 18:19:27 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-393919</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-393919</link>
      <description>EUVD-2026-393919</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-393919</guid>
    </item>
    <item>
      <title>fkie_cve-2026-71195</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-71195</link>
      <description>&lt;p&gt;In OpenStack Manila before 23.0.1, multiple Manila API operations on public shares do not verify that the caller owns the share. The API controllers authorize operations against the caller&amp;#39;s own project context, then load a foreign public share without re-authorizing against the share&amp;#39;s actual owner. This affects the following operations: allow_access: grant data-plane read/write access to another tenant&amp;#39;s share; deny_access: revoke the owner&amp;#39;s existing access rules; update_access: escalate access level (e.g., ro to rw); create_share_backup: exfiltrate share data via a backup created under the attacker&amp;#39;s project; soft_delete: move a foreign share to the recycle bin; restore: interfere with the owner&amp;#39;s deletion workflow; export location metadata: create, update, and delete metadata on foreign export locations; access rule listing: disclose IPs, usernames, and CephFS keys. Any authenticated project member can exploit these operations on any public share. The share UUID is visible since the share is public.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In OpenStack Manila before 23.0.1, multiple Manila API operations on public shares do not verify that the caller owns the share. The API controllers authorize operations against the caller&amp;#39;s own project context, then load a foreign public share without re-authorizing against the share&amp;#39;s actual owner. This affects the following operations: allow_access: grant data-plane read/write access to another tenant&amp;#39;s share; deny_access: revoke the owner&amp;#39;s existing access rules; update_access: escalate access level (e.g., ro to rw); create_share_backup: exfiltrate share data via a backup created under the attacker&amp;#39;s project; soft_delete: move a foreign share to the recycle bin; restore: interfere with the owner&amp;#39;s deletion workflow; export location metadata: create, update, and delete metadata on foreign export locations; access rule listing: disclose IPs, usernames, and CephFS keys. Any authenticated project member can exploit these operations on any public share. The share UUID is visible since the share is public.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-71195</guid>
    </item>
    <item>
      <title>GHSA-xm2x-8fhq-8hpv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xm2x-8fhq-8hpv</link>
      <description>&lt;p&gt;In OpenStack Manila before 23.0.1, multiple Manila API operations on public shares do not verify that the caller owns the share. The API controllers authorize operations against the caller&amp;#39;s own project context, then load a foreign public share without re-authorizing against the share&amp;#39;s actual owner. This affects the following operations: allow_access: grant data-plane read/write access to another tenant&amp;#39;s share; deny_access: revoke the owner&amp;#39;s existing access rules; update_access: escalate access level (e.g., ro to rw); create_share_backup: exfiltrate share data via a backup created under the attacker&amp;#39;s project; soft_delete: move a foreign share to the recycle bin; restore: interfere with the owner&amp;#39;s deletion workflow; export location metadata: create, update, and delete metadata on foreign export locations; access rule listing: disclose IPs, usernames, and CephFS keys. Any authenticated project member can exploit these operations on any public share. The share UUID is visible since the share is public.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In OpenStack Manila before 23.0.1, multiple Manila API operations on public shares do not verify that the caller owns the share. The API controllers authorize operations against the caller&amp;#39;s own project context, then load a foreign public share without re-authorizing against the share&amp;#39;s actual owner. This affects the following operations: allow_access: grant data-plane read/write access to another tenant&amp;#39;s share; deny_access: revoke the owner&amp;#39;s existing access rules; update_access: escalate access level (e.g., ro to rw); create_share_backup: exfiltrate share data via a backup created under the attacker&amp;#39;s project; soft_delete: move a foreign share to the recycle bin; restore: interfere with the owner&amp;#39;s deletion workflow; export location metadata: create, update, and delete metadata on foreign export locations; access rule listing: disclose IPs, usernames, and CephFS keys. Any authenticated project member can exploit these operations on any public share. The share UUID is visible since the share is public.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xm2x-8fhq-8hpv</guid>
    </item>
    <item>
      <title>RHSA-2026:99947 — Red Hat Security Advisory: Red Hat OpenStack Platform 17.1 (openstack-manila) security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:99947</link>
      <description>&lt;p&gt;manila: manila: Public Manila Share Allows Cross-Project Access-Rule and  Export-Metadata Writes&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;manila: manila: Public Manila Share Allows Cross-Project Access-Rule and  Export-Metadata Writes&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:99947</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-71195</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-71195</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: manila, Ubuntu:18.04:LTS: manila, Ubuntu:20.04:LTS: manila, Ubuntu:22.04:LTS: manila, Ubuntu:24.04:LTS: manila, Ubuntu:26.10: manila, Ubuntu:26.04:LTS: manila&lt;/p&gt;
&lt;p&gt;In OpenStack Manila before 23.0.1, multiple Manila API operations on public shares do not verify that the caller owns the share. The API controllers authorize operations against the caller&amp;#39;s own project context, then load a foreign public share without re-authorizing against the share&amp;#39;s actual owner. This affects the following operations: allow_access: grant data-plane read/write access to another tenant&amp;#39;s share; deny_access: revoke the owner&amp;#39;s existing access rules; update_access: escalate access level (e.g., ro to rw); create_share_backup: exfiltrate share data via a backup created under the attacker&amp;#39;s project; soft_delete: move a foreign share to the recycle bin; restore: interfere with the owner&amp;#39;s deletion workflow; export location metadata: create, update, and delete metadata on foreign export locations; access rule listing: disclose IPs, usernames, and CephFS keys. Any authenticated project member can exploit these operations on any public share. The share UUID is visible since the share is public.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: manila, Ubuntu:18.04:LTS: manila, Ubuntu:20.04:LTS: manila, Ubuntu:22.04:LTS: manila, Ubuntu:24.04:LTS: manila, Ubuntu:26.10: manila, Ubuntu:26.04:LTS: manila&lt;/p&gt;
&lt;p&gt;In OpenStack Manila before 23.0.1, multiple Manila API operations on public shares do not verify that the caller owns the share. The API controllers authorize operations against the caller&amp;#39;s own project context, then load a foreign public share without re-authorizing against the share&amp;#39;s actual owner. This affects the following operations: allow_access: grant data-plane read/write access to another tenant&amp;#39;s share; deny_access: revoke the owner&amp;#39;s existing access rules; update_access: escalate access level (e.g., ro to rw); create_share_backup: exfiltrate share data via a backup created under the attacker&amp;#39;s project; soft_delete: move a foreign share to the recycle bin; restore: interfere with the owner&amp;#39;s deletion workflow; export location metadata: create, update, and delete metadata on foreign export locations; access rule listing: disclose IPs, usernames, and CephFS keys. Any authenticated project member can exploit these operations on any public share. The share UUID is visible since the share is public.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-71195</guid>
    </item>
  </channel>
</rss>
