{"vuln_id":"GHSA-rxhg-2pw9-vf25","aliases":[],"description":"Send max_access_count can be exceeded by concurrent access requests","published_at":"2026-10-03T20:58:17Z","modified_at":"2026-10-03T21:03:42Z","first_seen_at":"2026-11-22T13:40:16.271585Z","severity":"medium","severity_source":"ghsa","cvss_score":5.3,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","cwe":["CWE-362"],"vendor":null,"product":null,"kev":{"is_kev":false,"date_added":null,"due_date":null,"ransomware":false},"epss":null,"epss_percentile":null,"nvd_status":null,"enriched_at":null,"links":{"nvd":"https://github.com/advisories/GHSA-rxhg-2pw9-vf25"},"matched_alias":null,"items":[{"id":12042,"source":{"id":"gh-vaultwarden","name":"Vaultwarden releases + advisories (GitHub dani-garcia/vaultwarden)"},"title":"GHSA-rxhg-2pw9-vf25: Send max_access_count can be exceeded by concurrent access requests","summary":"Send max_access_count can be exceeded by concurrent access requests\n\n### Summary\r\n\r\nVaultwarden does not enforce a Send's `max_access_count` atomically. The access-count check and the increment are separate operations, so concurrent requests can all pass the check before any of them writes, allowing more accesses than the sender configured.\r\n\r\n### Details\r\n\r\n**File:** `src/api/core/sends.rs`\r\n\r\nBoth Send access endpoints read `access_count`, compare it against `max_access_count`, then write `access_count + 1` as a separate operation, with no database-level locking:\r\n\r\n```rust\r\n// Read (check):\r\nif let Some(max_access_count) = send.max_access_count\r\n    && send.access_count >= max_access_count { ... }\r\n// Write (increment — separate DB operation):\r\nsend.access_count += 1;\r\nsend.save(&conn).await?;\r\n```\r\n\r\nTwo concurrent requests against a Send at `access_count = 0, max_access_count = 1`: both read `0`, both pass the check, and both write `access_count = 1`. Both return the secret — the text content for a text Send, or a signed download token for a file Send.\r\n\r\nThe write compounds the problem. `save()` persists the whole row from memory, so one request's stale in-memory value overwrites another's increment rather than adding to it. The stored counter can therefore under-report the number of accesses that actually succeeded.\r\n\r\n### Reproduction\r\n\r\nCreate a Send with `maxAccessCount: 1`, then issue many concurrent access requests for it. Before the fix, more than one request returns 200 while the stored `access_count` advances only once — the whole-row save overwriting the concurrent increment. After the fix, exactly one request succeeds and the rest return 404.\r\n\r\n### Impact\r\n\r\n- A Send capped at a given number of accesses can be accessed more times than configured, by anyone holding the Send link.\r\n- For text Sends, two parties can simultaneously claim the \"last\" access and both receive the content.\r\n- The sender's intent in setting `maxAccessCount` is not reliably enforced.\r\n\r\n### Fix\r\n\r\nFixed in 1.37.0 (`46ae59ea`, #7472). `Send::register_access` (`src/db/models/send.rs`) performs the check and the increment as a single conditional statement:\r\n\r\n```rust\r\ndiesel::update(sends::table)\r\n    .filter(sends::uuid.eq(uuid))\r\n    .filter(\r\n        sends::max_access_count\r\n            .is_null()\r\n            .or(sends::access_count.nullable().lt(sends::max_access_count)),\r\n    )\r\n    .set((sends::access_count.eq(sends::access_count + 1), sends::revision_date.eq(revision_date)))\r\n    .execute(conn)\r\n```\r\n\r\nZero affected rows means the limit was already reached, which every access path turns into the existing 404. In 1.37.0 one path still wrote the whole row: the legacy access route (`post_access_legacy`) called `save()` for file Sends, which could overwrite a concurrent increment.\n\nAffected packages: rust:vaultwarden\nPatched: vaultwarden 1.37.0","url":"https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-rxhg-2pw9-vf25","published_at":"2026-10-03T20:58:17Z","updated_at":"2026-10-03T21:03:42Z","fetched_at":"2026-11-22T13:40:16.224709Z","severity":"medium","cvss_score":5.3,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"dani-garcia","product":"vaultwarden","vuln_id":"GHSA-rxhg-2pw9-vf25","vuln_ids":["GHSA-RXHG-2PW9-VF25"],"tags":["repo-advisory","rust","CWE-362","security","repo:dani-garcia/vaultwarden"],"cluster_id":11354,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12042","html":"https://vulnwatch.ve1ve2.com/item/12042"}},{"id":12710,"source":{"id":"gh-vaultwarden","name":"Vaultwarden releases + advisories (GitHub dani-garcia/vaultwarden)"},"title":"[SECURITY RELEASE] dani-garcia/vaultwarden 1.37.0","summary":"Fixes advisories: GHSA-hw4g-2v3f-74x5, GHSA-rxhg-2pw9-vf25, GHSA-455c-vgg9-jxw8, GHSA-wc45-m6pv-rrf9, GHSA-rqf8-2568-r7mc, GHSA-88qc-6ch9-mc3j, GHSA-xwf8-pjh7-h589, GHSA-vh5m-fc9v-m84g, GHSA-f3qw-qg77-hmm4, GHSA-96f7-78q5-j345, GHSA-jq2g-h4xr-4mcr\n\nSecurity keywords: security, ssrf, GHSA-HW4G-2V3F-74X5, GHSA-VH5M-FC9V-M84G, GHSA-XWF8-PJH7-H589, GHSA-88QC-6CH9-MC3J, GHSA-RXHG-2PW9-VF25, GHSA-96F7-78Q5-J345, GHSA-455C-VGG9-JXW8, GHSA-F3QW-QG77-HMM4, GHSA-JQ2G-H4XR-4MCR, GHSA-RQF8-2568-R7MC\n\n## Note\r\nThis update is required for support with clients with version 2026.7.0+, please update before reporting any issues with them.\r\n\r\n## Security Fixes\r\nThis release contains security fixes for the following advisories. We strongly advice to update as soon as possible.\r\n- SSRF via the icon endpoint [[GHSA-hw4g-2v3f-74x5]](https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-hw4g-2v3f-74x5) [[GHSA-vh5m-fc9v-m84g]](https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-vh5m-fc9v-m84g) (**Medium**, 5.8 / 6.3)\r\n- Cross-Organization Cipher Access [[GHSA-xwf8-pjh7-h589]](https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-xwf8-pjh7-h589) (**Medium**, 5.9)\r\n- Organization Policy Bypass on Directory Import [[GHSA-88qc-6ch9-mc3j]](https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-88qc-6ch9-mc3j) (**Medium**, 5.5)\r\n- Send Access-Count Bypass [[GHSA-rxhg-2pw9-vf25]](https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-rxhg-2pw9-vf25) (**Medium**, 5.3)\r\n- Unauthenticated WebSocket Flooding DDOS [[GHSA-96f7-78q5-j345]](https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-96f7-78q5-j345) (**Medium**, 5.3)\r\n- Cross-Organization Secret Sharing [[GHSA-455c-vgg9-jxw8]](https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-455c-vgg9-jxw8) (**Medium**, 4.3)\r\n- Organization Import Authorization [[GHSA-f3qw-qg77-hmm4]](https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-f3qw-qg77-hmm4)[[GHSA-jq2g-h4xr-4mcr]](https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-jq2g-h4xr-4mcr) (**Medium**, 4.3)\r\n- Organization Data Enumeration via the Manager role [[GHSA-rqf8-2568-r7mc]](https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-rqf8-2568-r7mc) (**Medium**, 4.3)\r\n\r\nThese are private for now, pending CVE assignment and publishing at a later date.\r\n\r\n## What's Changed\r\n* OpenDAL S3 parameter support by @txase in https://github.com/dani-garcia/vaultwarden/pull/6127\r\n* Fix SSO Cookie path by @BlackDex in https://github.com/dani-garcia/vaultwarden/pull/7187\r\n* fix email 2fa for bw cli by @stefan0xC in https://github.com/dani-garcia/vaultwarden/pull/7225\r\n* sso_auth improvements by @Timshel in https://github.com/dani-garcia/vaultwarden/pull/7197\r\n* Reject unrecognised DATABASE_URL instead of silent SQLite fallback by @mfw78 in https://github.com/dani-garcia/vaultwarden/pull/7061\r\n* Switch to `xx-cargo` by @dfunkt in https://github.com/dani-garcia/vaultwarden/pull/6640\r\n* Updates and fixes by @BlackDex in https://github.com/dani-garcia/vaultwarden/pull/7235\r\n* Switch to Edition 2024, more clippy lints, and less macro calls by @BlackDex in https://github.com/dani-garcia/vaultwarden/pull/7200\r\n* Serve Apple app site association file by @user71424q in https://github.com/dani-garcia/vaultwarden/pull/7191\r\n* Update Rust, Crates and GHA by @BlackDex in https://github.com/dani-garcia/vaultwarden/pull/7307\r\n* Fix enforce blocked by @Timshel in https://github.com/dani-garcia/vaultwarden/pull/7246\r\n* Admin password recovery endpoint change by @Timshel in https://github.com/dani-garcia/vaultwarden/pull/7270\r\n* fix(sends): emit hideEmail as non-null boolean in sync response by @kvdb in https://github.com/dani-garcia/vaultwarden/pull/7283\r\n* Org membership delete remove Invitation by @Timshel in https://github.com/dani-garcia/vaultwarden/pull/7284\r\n* [v2026.5.0] Registration request update by @Timshel in https://github.com/dani-garcia/vaultwarden/pull/7295\r\n* [v2026.5.0] PutPolicy now using vnext format by @Timshel in https://github.com/dani-garcia/vaultwarden/pull/7296\r\n* 2026.6.0 send support by @Timshel in https://github.com/dani-garcia/vaultwarden/pull/7346\r\n* Add SSO_AUTHORIZE_BODY by @Timshel in https://github.com/dani-garcia/vaultwarden/pull/7357\r\n* Add `pm-26340-linux-biometrics-v2` feature flag by @pilotstew in https://github.com/dani-garcia/vaultwarden/pull/7358\r\n* improve CI by @TriplEight in https://github.com","url":"https://github.com/dani-garcia/vaultwarden/releases/tag/1.37.0","published_at":"2026-07-24T17:04:39Z","updated_at":null,"fetched_at":"2026-11-22T14:05:38.135281Z","severity":"medium","cvss_score":5.9,"epss":0.0033,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"dani-garcia","product":"vaultwarden","vuln_id":"CVE-2026-116678","vuln_ids":["CVE-2026-116678","CVE-2026-33420","CVE-2026-47160","GHSA-455C-VGG9-JXW8","GHSA-72VH-X5JQ-M82G","GHSA-88QC-6CH9-MC3J","GHSA-96F7-78Q5-J345","GHSA-F3QW-QG77-HMM4","GHSA-HW4G-2V3F-74X5","GHSA-JJXG-P3V6-52WW","GHSA-JQ2G-H4XR-4MCR","GHSA-RQF8-2568-R7MC","GHSA-RXHG-2PW9-VF25","GHSA-VH5M-FC9V-M84G","GHSA-WC45-M6PV-RRF9","GHSA-XWF8-PJH7-H589"],"tags":["release","repo:dani-garcia/vaultwarden","security","stack","vaultwarden"],"cluster_id":11350,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12710","html":"https://vulnwatch.ve1ve2.com/item/12710"}}]}