<?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>Tue, 06 Oct 2026 14:01:33 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-274633</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-274633</link>
      <description>EUVD-2026-274633</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-274633</guid>
    </item>
    <item>
      <title>fkie_cve-2026-27803</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-27803</link>
      <description>&lt;p&gt;Vaultwarden is an unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs. Prior to version 1.35.4, when a Manager has manage=false for a given collection, they can still perform several management operations as long as they have access to the collection. This issue has been patched in version 1.35.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Vaultwarden is an unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs. Prior to version 1.35.4, when a Manager has manage=false for a given collection, they can still perform several management operations as long as they have access to the collection. This issue has been patched in version 1.35.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-27803</guid>
    </item>
    <item>
      <title>GHSA-h4hq-rgvh-wh27 — Vaultwarden's Collection Management Operations Allowed Without `manage` Verification for Manager Role</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h4hq-rgvh-wh27</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: vaultwarden&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Testing confirmed that even when a Manager has `manage=false` for a given collection, they can still perform the following management operations as long as they have access to the collection:&lt;/p&gt;
&lt;p&gt;* `PUT /api/organizations/&amp;lt;org_id&amp;gt;/collections/&amp;lt;col_id&amp;gt;` succeeds (HTTP 200)
* `PUT /api/organizations/&amp;lt;org_id&amp;gt;/collections/&amp;lt;col_id&amp;gt;/users` succeeds (HTTP 200)
* `DELETE /api/organizations/&amp;lt;org_id&amp;gt;/collections/&amp;lt;col_id&amp;gt;` succeeds (HTTP 200)&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;* The Manager guard checks only whether the user **can access the collection**, not whether they have `manage` privileges. This check is directly applied to management endpoints.
src/auth.rs:816
  ```rust&lt;/p&gt;
&lt;p&gt;if !Collection::can_access_collection(&amp;amp;headers.membership, &amp;amp;col_id, &amp;amp;conn).await {
      err_handler!(&amp;#34;The current user isn&amp;#39;t a manager for this collection&amp;#34;)
  }
  ```&lt;/p&gt;
&lt;p&gt;* The `can_access_collection` function does **not** evaluate the `manage` flag.
  src/db/models/collection.rs:140&lt;/p&gt;
&lt;p&gt;```rust&lt;/p&gt;
&lt;p&gt;pub async fn can_access_collection(member: &amp;amp;Membership, col_id: &amp;amp;CollectionId, conn: &amp;amp;DbConn) -&amp;gt; bool {
      member.has_status(MembershipStatus::Confirmed)
          &amp;amp;&amp;amp; (member.has_full_access()
              || CollectionUser::has_access_to_collection_by_user(col_id, &amp;amp;member.user_uuid, conn).await
              || ...
  ```&lt;/p&gt;
&lt;p&gt;* A separate management-permission check exists and includes `manage` validation, but it is **not used** during authorization for the affected endpoints.
  src/db/models/collection.rs:516&lt;/p&gt;
&lt;p&gt;```rust…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: vaultwarden&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Testing confirmed that even when a Manager has `manage=false` for a given collection, they can still perform the following management operations as long as they have access to the collection:&lt;/p&gt;
&lt;p&gt;* `PUT /api/organizations/&amp;lt;org_id&amp;gt;/collections/&amp;lt;col_id&amp;gt;` succeeds (HTTP 200)
* `PUT /api/organizations/&amp;lt;org_id&amp;gt;/collections/&amp;lt;col_id&amp;gt;/users` succeeds (HTTP 200)
* `DELETE /api/organizations/&amp;lt;org_id&amp;gt;/collections/&amp;lt;col_id&amp;gt;` succeeds (HTTP 200)&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;* The Manager guard checks only whether the user **can access the collection**, not whether they have `manage` privileges. This check is directly applied to management endpoints.
src/auth.rs:816
  ```rust&lt;/p&gt;
&lt;p&gt;if !Collection::can_access_collection(&amp;amp;headers.membership, &amp;amp;col_id, &amp;amp;conn).await {
      err_handler!(&amp;#34;The current user isn&amp;#39;t a manager for this collection&amp;#34;)
  }
  ```&lt;/p&gt;
&lt;p&gt;* The `can_access_collection` function does **not** evaluate the `manage` flag.
  src/db/models/collection.rs:140&lt;/p&gt;
&lt;p&gt;```rust&lt;/p&gt;
&lt;p&gt;pub async fn can_access_collection(member: &amp;amp;Membership, col_id: &amp;amp;CollectionId, conn: &amp;amp;DbConn) -&amp;gt; bool {
      member.has_status(MembershipStatus::Confirmed)
          &amp;amp;&amp;amp; (member.has_full_access()
              || CollectionUser::has_access_to_collection_by_user(col_id, &amp;amp;member.user_uuid, conn).await
              || ...
  ```&lt;/p&gt;
&lt;p&gt;* A separate management-permission check exists and includes `manage` validation, but it is **not used** during authorization for the affected endpoints.
  src/db/models/collection.rs:516&lt;/p&gt;
&lt;p&gt;```rust…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h4hq-rgvh-wh27</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0594 — Vaultwarden: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0594</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Vaultwarden ausnutzen, um Sicherheitsmaßnahmen zu umgehen, erweiterte Privilegien zu erlangen, vertrauliche Informationen offenzulegen und Daten zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Vaultwarden ausnutzen, um Sicherheitsmaßnahmen zu umgehen, erweiterte Privilegien zu erlangen, vertrauliche Informationen offenzulegen und Daten zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0594</guid>
    </item>
  </channel>
</rss>
