CVE-2026-48085

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.6% (48th 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
Elevated

Also known asEUVD-2026-54167 (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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: No code on recordExposed 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 version 1.0.1, a fully provisioned OpenReception instance accepts unauthenticated POST requests to /setup/create-admin-account and creates additional GLOBAL_ADMIN accounts without verifying that an admin already exists. Any unauthenticated network attacker who can submit a same-origin form POST gains full platform-level administrative control. The newly created account is is_active=true with confirmation_state=ACCESS_GRANTED and does not require completing email confirmation; the GLOBAL_ADMIN row is created active and immediately usable. Login and tenant enumeration succeed without any further interaction. This is distinct from the deployment race condition already documented on the Claiming an instance page. That documented race covers the window between deployment and first claim. The bug reported here works after the operator has properly claimed and configured the instance: the layout-level guard that protects the setup page only redirects on GET, while the default form action handler creates the user without rechecking adminExists(). Three GLOBAL_ADMIN accounts were created in succession during testing, with no rate limiting observed. Audit-specific event logging beyond standard application logs was not assessed; the standard [error] line that surfaces only when a uniqueness conflict is hit is not the same as a security event for "additional admin created post-claim". The form post is rejected for browser drive-by CSRF by SvelteKit's built-in same-origin check, but any tool that supplies a matching Origin header (curl, Burp, automated scanners, server-side proxies) bypasses this trivially. No additional preconditions exist. Users should upgrade to version 1.0.1 to receive a patch.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (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 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.6%
EPSS %ILE
48th
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.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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, Track* at medium and Attend at high mission impact.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, 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 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

August 6, 2026

Last Modified

October 23, 2026

Advisory Details (2)

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

unauthenticated GLOBAL_ADMIN account creation post-bootstrap · Advisory · open-reception/appointment-booking-software · GitHub

https://github.com/open-reception/appointment-booking-software/security/advisories/GHSA-qvvq-hhpj-64rp
GitHub commit Patch Available

commit 222408af6fd4 (open-reception/appointment-booking-software)

Patch available: open-reception/appointment-booking-software v1.0.1 (contains commit 222408af6fd4)

https://github.com/open-reception/appointment-booking-software/commit/222408af6fd4bd85554a25ec8de8131bd0733797

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 181 rows 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 81 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-48085?
CVE-2026-48085 is a critical-severity vulnerability; its CVE record was published on August 6, 2026. OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to version 1.0.1, a fully provisioned OpenReception instance accepts unauthenticated POST requests to /setup/create-admin-account and creates additional GLOBAL_ADMIN accounts without…
When was the CVE record for CVE-2026-48085 published?
The CVE record for CVE-2026-48085 was published on August 6, 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 October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-48085 actively exploited?
CVE-2026-48085 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48085?
CVE-2026-48085 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-48085?
A fix for CVE-2026-48085 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-48085

Explore →

Is Your Infrastructure Affected by CVE-2026-48085?

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