CVE-2026-54460

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-82418 (ENISA EUVD)Source: ENISA EUVD

9.8EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to 1.1.1, POST /api/auth/passkeys accepts a request-body userId and attacker-supplied passkey without an authenticated session, does not call WebAuthnService.verifyRegistration, and does not bind enrollment to locals.user.id. An unauthenticated attacker who knows the public tenant ID and the target staff email can use the public booking bootstrap and GET /api/tenants/[id]/appointments/staff-public-keys to obtain candidate userId values. The attacker first causes UserService.addAdditionalPasskey to store a controlled public key for a candidate userId, then attempts login with the target email; the login check compares verificationResult.userId with the email-resolved account and reveals whether the injected credential belongs to that target. Repeating this injection-before-login sequence identifies the matching userId, and the normal login endpoint accepts the attacker's assertion for the stored key and creates a STAFF session. The session can expose tenant data and reveal TENANT_ADMIN identifiers for further takeover; GLOBAL_ADMIN accounts are not reachable through this tenant-scoped path. A hijacked TENANT_ADMIN can modify or delete tenant resources and key shares, potentially making appointment data permanently undecryptable and taking booking services offline. This issue is fixed in version 1.1.1.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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.7%
EPSS %ILE
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

September 17, 2026

Last Modified

September 30, 2026

Advisory Details (5)

Auto-updated Oct 31, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Unauthenticated WebAuthn passkey injection via `POST /api/auth/passkeys` leads to account takeover · Advisory · open-reception/appointment-booking-software · GitHub

https://github.com/open-reception/appointment-booking-software/security/advisories/GHSA-g233-m625-m3pc
GitHub release Patch Available

v1.1.1 Critical Security Update

Patch available: open-reception/appointment-booking-software v1.1.1

https://github.com/open-reception/appointment-booking-software/releases/tag/v1.1.1
GitHub commit Patch Available

commit 93040884b783 (open-reception/appointment-booking-software)

Patch available: open-reception/appointment-booking-software v1.1.1 (contains commit 93040884b783)

https://github.com/open-reception/appointment-booking-software/commit/93040884b783573dbf161723e508676327fdf0bf
GitHub commit Patch Available

commit 5d29d9c1964e (open-reception/appointment-booking-software)

Patch available: open-reception/appointment-booking-software v1.1.1 (contains commit 5d29d9c1964e)

https://github.com/open-reception/appointment-booking-software/commit/5d29d9c1964ef7541a6e96d04d946c22f76eea00

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 63× 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.

  1. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-02 08:11 UTCEG score recompute
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-11-01 06:59 UTCEG score recompute
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-10-31 05:47 UTCEG score recompute
  7. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-10-30 04:34 UTCEG score recompute
  9. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-10-29 03:21 UTCEG score recompute
  11. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-10-28 02:09 UTCEG score recompute
  13. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-10-27 00:53 UTCEG score recompute
  15. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-25 19:57 UTCEG score recompute
  17. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-25 14:19 UTCEG score recompute
  19. 2026-10-24 18:43 UTCEG score recompute
  20. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-23 17:31 UTCEG score recompute
  22. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-22 16:18 UTCEG score recompute
  25. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
Show 72 more
  1. 2026-10-21 14:25 UTCEG score recompute
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-10-20 13:12 UTCEG score recompute
  4. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-10-19 11:57 UTCEG score recompute
  6. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-10-18 03:31 UTCEG score recompute
  8. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-17 08:47 UTCEG score recompute
  10. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-16 07:33 UTCEG score recompute
  12. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-15 06:18 UTCEG score recompute
  14. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-10-14 01:58 UTCEG score recompute
  16. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-10-12 22:15 UTCEG score recompute
  18. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-10-12 15:56 UTCEG score recompute
  20. 2026-10-11 19:39 UTCEG score recompute
  21. 2026-10-11 16:54 UTCEG score recompute
  22. 2026-10-11 14:18 UTCEG score recompute
  23. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-10-11 11:38 UTCEG score recompute
  25. 2026-10-10 20:44 UTCEG score recompute
  26. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-10-09 22:23 UTCEG score recompute
  28. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  29. 2026-10-08 17:39 UTCEG score recompute
  30. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  31. 2026-10-08 03:34 UTCEG score recompute
  32. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  33. 2026-10-06 15:46 UTCEG score recompute
  34. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  35. 2026-10-05 21:45 UTCEG score recompute
  36. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  37. 2026-10-05 03:44 UTCEG score recompute
  38. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  39. 2026-10-03 16:12 UTCEG score recompute
  40. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  41. 2026-10-02 17:57 UTCEG score recompute
  42. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  43. 2026-10-01 20:02 UTCEG score recompute
  44. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  45. 2026-09-30 17:49 UTCEG score recompute
  46. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  47. 2026-09-29 16:13 UTCEG score recompute
  48. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  49. 2026-09-28 22:41 UTCEG score recompute
  50. 2026-09-28 18:17 UTCEG score recompute
  51. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  52. 2026-09-27 15:46 UTCEG score recompute
  53. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  54. 2026-09-26 17:47 UTCEG score recompute
  55. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  56. 2026-09-26 04:27 UTCEG score recompute
  57. 2026-09-24 21:24 UTCEG score recompute
  58. 2026-09-24 20:57 UTCEG score recompute
  59. 2026-09-24 15:18 UTCEG score recompute
  60. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  61. 2026-09-23 21:49 UTCEG score recompute
  62. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  63. 2026-09-22 15:05 UTCEG score recompute
  64. 2026-09-21 21:37 UTCEG score recompute
  65. 2026-09-20 23:42 UTCEG score recompute
  66. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  67. 2026-09-19 17:04 UTCEG score recompute
  68. 2026-09-18 23:33 UTCEG score recompute
  69. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  70. 2026-09-17 21:20 UTCEG score recompute
  71. 2026-09-17 20:25 UTCEG score recomputeFirst assessed: 9.8 CRITICAL
  72. 2026-09-17 20:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54460?
CVE-2026-54460 is a critical-severity vulnerability; its CVE record was published on September 17, 2026. OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to 1.1.1, POST /api/auth/passkeys accepts a request-body userId and attacker-supplied passkey without an authenticated session, does not call WebAuthnService.verifyRegistration, and…
When was the CVE record for CVE-2026-54460 published?
The CVE record for CVE-2026-54460 was published on September 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-54460 actively exploited?
CVE-2026-54460 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54460?
CVE-2026-54460 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54460?
A fix for CVE-2026-54460 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54460?

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