{"vuln_id":"GHSA-64mc-4p6f-r7x9","aliases":[],"description":"Revoked or unconfirmed organization Admin can read cipher audit logs","published_at":"2026-10-28T18:00:44Z","modified_at":"2026-10-28T18:00:44Z","first_seen_at":"2026-11-22T13:40:16.266018Z","severity":"medium","severity_source":"ghsa","cvss_score":4.3,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","cwe":["CWE-863"],"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-64mc-4p6f-r7x9"},"matched_alias":null,"items":[{"id":12038,"source":{"id":"gh-vaultwarden","name":"Vaultwarden releases + advisories (GitHub dani-garcia/vaultwarden)"},"title":"GHSA-64mc-4p6f-r7x9: Revoked or unconfirmed organization Admin can read cipher audit logs","summary":"Revoked or unconfirmed organization Admin can read cipher audit logs ## Summary `GET /api/ciphers//events` returns an organization cipher's audit log to any authenticated user whose membership row carries `atype` Owner or Admin, **regardless of membership status**. A member who was invited but never confirmed, or who was confirmed and later revoked, keeps indefinite read access to that cipher's access history: who viewed, edited, copied or autofilled the credential, when, from which IP and device type. The two sibling event endpoints in the same file are guarded correctly. This one is not. Requires `ORG_EVENTS_ENABLED=true`, which is not the default. ## Affected 1.37.3 (current release) and `main` at commit `25dfedaf` (2026-09-09). Verified on both. ## Root cause `src/api/core/events.rs` has three event endpoints. Two require `AdminHeaders`: ```rust :34 async fn get_org_events(..., headers: AdminHeaders, ...) // organization events :92 async fn get_user_events(..., headers: AdminHeaders, ...) // per member events :66 async fn get_cipher_events(..., headers: Headers, ...) // per cipher events ``` `AdminHeaders` resolves through `is_confirmed_and_admin()` at `src/auth.rs:725`: ```rust fn is_confirmed_and_admin(&self) -> bool { self.membership_status == MembershipStatus::Confirmed && self.membership_type >= MembershipType::Admin } ``` `get_cipher_events` instead takes the generic `Headers` guard, which only proves a valid user JWT, and hand rolls its own check via `Membership::user_has_ge_admin_access_to_cipher` at `src/db/models/organization.rs:1105`: ```rust users_organizations::table .inner_join(ciphers::table.on(ciphers::uuid.eq(cipher_uuid) .and(ciphers::organization_uuid.eq(users_organizations::org_uuid.nullable())))) .filter(users_organizations::user_uuid.eq(user_uuid)) .filter(users_organizations::atype.eq_any(vec![MembershipType::Owner as i32, MembershipType::Admin as i32])) ``` That reproduces the `membership_type >= Admin` half of `is_confirmed_and_admin` and drops the `membership_status == Confirmed` half. Every other membership query in `organization.rs` states the invariant in its own name and enforces it: `find_confirmed_by_user`, `find_confirmed_by_user_and_org`, `find_confirmed_by_org`, `find_confirmed_and_manage_all_by_org`, `count_confirmed_by_org_and_type`, `find_by_user_and_policy`. The one function that deliberately omits it is named `find_any_state_by_user`. `user_has_ge_admin_access_to_cipher` omits it without saying so. Upstream Bitwarden gates the equivalent endpoint with the same check it uses for organization events (`src/Api/Dirt/Controllers/EventsController.cs`, `AccessEventLogs`). The comment at `src/api/core/events.rs:32` cites that controller as the reference implementation. ## Steps to Reproduce ``` docker run -d --name vw-repro \\ -e ORG_EVENTS_ENABLED=true -e SIGNUPS_ALLOWED=true \\ -e I_REALLY_W Affected packages: rust:vaultwarden Patched: vaultwarden 1.37.4","url":"https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-64mc-4p6f-r7x9","published_at":"2026-10-28T18:00:44Z","updated_at":"2026-10-28T18:00:44Z","fetched_at":"2026-11-22T13:40:16.224699Z","severity":"medium","cvss_score":4.3,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"dani-garcia","product":"vaultwarden","vuln_id":"GHSA-64mc-4p6f-r7x9","vuln_ids":["GHSA-64MC-4P6F-R7X9"],"tags":["repo-advisory","rust","CWE-863","security","repo:dani-garcia/vaultwarden"],"cluster_id":11347,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12038","html":"https://vulnwatch.ve1ve2.com/item/12038"}},{"id":12065,"source":{"id":"gh-vaultwarden","name":"Vaultwarden releases + advisories (GitHub dani-garcia/vaultwarden)"},"title":"[SECURITY RELEASE] dani-garcia/vaultwarden 1.37.4","summary":"Fixes advisories: GHSA-7ccc-c43j-4p36, GHSA-69q9-v8p6-xvx3, GHSA-q5x6-grh5-fqgc, GHSA-v576-3wvq-xh3c, GHSA-64mc-4p6f-r7x9, GHSA-qwx4-wcv4-mpcv, GHSA-7jg8-8m5x-6j9r\n\nSecurity keywords: security, GHSA-69Q9-V8P6-XVX3, GHSA-7JG8-8M5X-6J9R, GHSA-V576-3WVQ-XH3C, GHSA-Q5X6-GRH5-FQGC, GHSA-64MC-4P6F-R7X9, GHSA-7CCC-C43J-4P36, GHSA-QWX4-WCV4-MPCV\n\nSecurity Fixes\n\nThis release contains security fixes for the following advisories. We strongly advise updating as soon as possible.\n\nOrganization member revocation [GHSA-69q9-v8p6-xvx3] (High, 8.1)\n\nTwo-factor authentication [GHSA-7jg8-8m5x-6j9r] (Medium, 6.8)\n\nOrganization invitations [GHSA-v576-3wvq-xh3c] (Medium, 6.8)\n\nAttachments [GHSA-q5x6-grh5-fqgc] (Medium, 6.5)\n\nOrganization event logs [GHSA-64mc-4p6f-r7x9] (Medium, 4.3)\n\nCipher sharing [GHSA-7ccc-c43j-4p36] (Medium, 4.3)\n\nOrganization API key [GHSA-qwx4-wcv4-mpcv] (Low, 3.8)\n\nAdditional dependency updates and minor security enhancements\n\nThese are private for now, pending CVE assignment and publishing at a later date.\n\nNote\n\nIf an organization has Admins you don't fully trust, consider rotating its API key after updating (Admin Console → Settings → Rotate API key). Before this release, Admins could also view the key.\n\nUpgrade notes\n\nReverse proxies: with IP_HEADER=X-Forwarded-For, the client IP is now the rightmost address that isn't in IP_HEADER_TRUSTED_PROXIES (it used to be the leftmost). If you have several proxies in a row, for example a CDN in front of nginx, add all of them to IP_HEADER_TRUSTED_PROXIES. Otherwise the address of the proxy in front is used for rate limiting and logs.\n\nSends: bw send receive on CLI 2026.4.2 and older no longer works, the same as against Bitwarden's own servers since v2026.8.0. Creating and managing Sends works on all clients.\n\nFeature flags: these flags were removed because no client reads them anymore: ssh-agent, ssh-key-vault-item, mutual-tls, anon-addy-self-host-alias, simple-login-self-host-alias, pm-25373-windows-biometrics-v2, pm-26340-linux-biometrics-v2, desktop-ui-migration-milestone-1 to -4, cxp-import-mobile and cxp-export-mobile. If EXPERIMENTAL_CLIENT_FEATURE_FLAGS still lists one of them, startup logs a warning and saving settings in the admin panel fails until it's removed.\n\nDuo: DUO_USE_IFRAME (the deprecated Traditional Prompt) is removed and ignored if set.\n\nCustom templates: there's a new email template, email/recover_twofactor, sent after a login with a two-step recovery code.\n\nThe legacy POST /identity/accounts/register and POST /api/accounts/prelogin endpoints are removed. No current client uses them.\n\nWhen using a MariaDB or MySQL server which does not support native TLS/SSL encrypted connections, using the Alpine image of Vaultwarden might fail to connect. Add MARIADB_TLS_DISABLE_PEER_VERIFICATION=1 as an environment variable to your Vaultwarden server environment, and it will start running again.\n\nWhat's Changed\n\n[Web 2026.9.0] Support the vault banner policy by @tom27052006 in #7748\n\nAdd support for basic auth response client feature flag by @tom27052006 in #7745\n\n[web-v2026.8.1] store the user key ID by @Timshel in #7693\n\nAdd organizationsNew and policiesNew to sync response by @tom27052006 in #7666\n\nAdd pm-32009-new-item-types feature flag by @bdd in #7478\n\nUpdate Crates, GHA and JS by @BlackDex in #7751\n\nAdd pm-34171-card-scanner feature flag by @bdd in #7477\n\nset user_created bool for each separate invitation by @stefan0xC in #7753\n\nFix revoked org members retaining access to org ciphers by @abhiShandy in #7554\n\nEnsure all user checked routes are confirmed by @dani-garcia in #7763\n\nFix cortex-a53 build issues when using xx-cargo by @BlackDex in #7774\n\nAdd undetermined-cipher-scenario-logic feature flag (closes #7801) by @cad0p in #7802\n\nAdd Windows native credential sync to supported feature flags by @KingIronMan2011 in #7798\n\nHide the whole change-email section when EMAIL_CHANGE_ALLOWED is false by @tom27052006 in #7759\n\nFix Clippy warnings across all targets by @tom27052006 in #7782\n\nAdmin reset: 2fa email fallback need a verified email by @Timshel in #7770\n\nSends cleanup: remove legacy endpoints and align with upstream by @dani-garcia in #7806\n\nRemove legacy API endpoints and compatibility code by @dani-garcia in #7809\n\nAlign API with upstream and remove unwraps by @dani-garcia in #7810\n\nUpdate cra","url":"https://github.com/dani-garcia/vaultwarden/releases/tag/1.37.4","published_at":"2026-10-06T11:30:54Z","updated_at":null,"fetched_at":"2026-11-22T13:40:16.224741Z","severity":"high","cvss_score":8.1,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"dani-garcia","product":"vaultwarden","vuln_id":"GHSA-69q9-v8p6-xvx3","vuln_ids":["GHSA-64MC-4P6F-R7X9","GHSA-69Q9-V8P6-XVX3","GHSA-7CCC-C43J-4P36","GHSA-7JG8-8M5X-6J9R","GHSA-Q5X6-GRH5-FQGC","GHSA-QWX4-WCV4-MPCV","GHSA-V576-3WVQ-XH3C"],"tags":["release","repo:dani-garcia/vaultwarden","security"],"cluster_id":11344,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12065","html":"https://vulnwatch.ve1ve2.com/item/12065"}}]}