CVE-2026-60104

HIGHNVD 8.08.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.0 under NVD CVSS v3. EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-08) is not newer than that change (2026-07-20), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
8.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Bitwarden Server before 2026.6.0 does not verify that the email in a POST /auth-requests/admin-request body belongs to the authenticated caller, allowing a low-privileged organization member to obtain another user's vault key and a victim-scoped access token by creating a Trusted Device Encryption authentication request, bound to an attacker-controlled public key, that is readable from an unauthenticated endpoint once approved resulting in disclosure of the victim's vault key and account takeover.

CVSS v3
8.0
EG Score
8.0HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity80% × 45%
The EG Score, 8.0 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 8, 2026

Last Modified

July 20, 2026

Advisory Details (5)

Auto-updated Jul 8, 2026
Patch available. Sources: github_commit, github_pr.
Web page

Bitwarden Server < 2026.6.0 Authorization Bypass via Admin Auth Request | Advisories | VulnCheck

https://www.vulncheck.com/advisories/bitwarden-server-authorization-bypass-via-admin-auth-request
Web page

Sanjok Karki | Offensive Security Engineer

https://sanjokkarki.com.np/blog/bitwarden-vault-key-heist
Web page

Releases · bitwarden/server · GitHub

https://github.com/bitwarden/server/releases#release-v2026.6.0
GitHub pull request Patch Available

[PM-35401] Update exception handling in CreateAuthRequestAsync() and PostAdminRequest()

Patch available: bitwarden/server v2026.6.0 (PR #7615 merged 2026-05-21)

https://github.com/bitwarden/server/pull/7615
GitHub commit Patch Available

commit dcf4c486b2b5 (bitwarden/server)

Patch available: bitwarden/server v2026.6.0 (contains commit dcf4c486b2b5)

https://github.com/bitwarden/server/commit/dcf4c486b2b5bedecc03a48b427243328cc74a9a

Vendor Advisories for CVE-2026-60104(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 239 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 139 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 19:35 UTCEG score recompute
  2. 2026-10-11 16:51 UTCEG score recompute
  3. 2026-10-11 14:13 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  7. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-01 16:10 UTCEG score recompute
  16. 2026-10-01 16:10 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  17. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-09-28 13:22 UTCEG score recompute
  20. 2026-09-28 13:22 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  21. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-09-24 11:47 UTCEG score recompute
  23. 2026-09-24 11:47 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  24. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-09-23 06:08 UTCEG score recompute
Show 75 more
  1. 2026-09-23 06:08 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  2. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  4. 2026-09-18 05:43 UTCEG score recompute
  5. 2026-09-18 05:43 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  6. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-09-14 11:15 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  11. 2026-09-13 23:49 UTCEG score recompute
  12. 2026-09-13 23:49 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  13. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-09-13 08:24 UTCEG score recompute
  15. 2026-09-13 08:24 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  16. 2026-09-12 14:44 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  17. 2026-09-12 03:32 UTCEG score recompute
  18. 2026-09-12 03:32 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  19. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-09-06 14:03 UTCEG score recompute
  24. 2026-09-06 14:03 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  25. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  26. 2026-09-05 22:47 UTCEG score recompute
  27. 2026-09-05 22:47 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  28. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  29. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  30. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  31. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  32. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  33. 2026-08-30 18:41 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  34. 2026-08-30 07:29 UTCEG score recompute
  35. 2026-08-30 07:29 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  36. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  37. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  38. 2026-08-27 21:49 UTCEG score recompute
  39. 2026-08-27 21:49 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  40. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  41. 2026-08-27 01:27 UTCEG score recompute
  42. 2026-08-27 01:27 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  43. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  44. 2026-08-26 08:22 UTCEG score recompute
  45. 2026-08-26 08:22 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  46. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  47. 2026-08-25 11:40 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  48. 2026-08-24 23:48 UTCEG score recompute
  49. 2026-08-24 23:48 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  50. 2026-08-24 12:37 UTCEG score recompute
  51. 2026-08-24 12:37 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  52. 2026-08-24 00:37 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  53. 2026-08-23 13:24 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  54. 2026-08-23 02:09 UTCEG score recompute
  55. 2026-08-23 02:08 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  56. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  57. 2026-08-22 14:57 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  58. 2026-08-22 03:46 UTCEG score recompute
  59. 2026-08-22 03:46 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  60. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  61. 2026-08-21 15:10 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  62. 2026-08-21 03:59 UTCEG score recompute
  63. 2026-08-21 03:59 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  64. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  65. 2026-08-20 15:37 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  66. 2026-08-20 01:58 UTCEG score recompute
  67. 2026-08-20 01:58 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  68. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  69. 2026-08-19 09:47 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  70. 2026-08-18 22:28 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  71. 2026-08-18 10:49 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  72. 2026-08-17 22:28 UTCEG score recompute
  73. 2026-08-17 22:28 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3
  74. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  75. 2026-08-17 07:40 UTCGHSA enrichmentGHSA-5g65-rmxf-rgj6 · GitHub severity HIGH · GitHub CVSS 7.3

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-60104?
CVE-2026-60104 is a high-severity vulnerability; its CVE record was published on July 8, 2026. Bitwarden Server before 2026.6.0 does not verify that the email in a POST /auth-requests/admin-request body belongs to the authenticated caller, allowing a low-privileged organization member to obtain another user's vault key and a victim-scoped access token by creating a Trusted Device Encryption…
When was CVE-2026-60104 made public?
CVE-2026-60104 was made public on May 12, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 8, 2026. EchelonGraph's copy of the record carries a last-modified date of July 20, 2026; the record at its source may have been updated since.
Is CVE-2026-60104 actively exploited?
CVE-2026-60104 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-60104?
CVE-2026-60104 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2026-60104?
A fix for CVE-2026-60104 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-60104 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-60104

Explore →

Is Your Infrastructure Affected by CVE-2026-60104?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs