OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. The new-client booking flow in versions 1.0.1 and prior consists of three calls: bootstrap-challenge (returns a 16-bit PoW challenge with difficulty=4 leading hex zeroes), bootstrap-verify (validates the PoW and issues a Bearer booking access token), and create-new-client (consumes the token and creates the tunnel and first appointment). The token correctly binds to tenantId, tunnelId, clientPublicKey, and emailHash, but never to channelId. The bootstrap-challenge request schema does not even accept a channelId, and the issued token's payload contains no channel information. Independently, the service function createNewClientWithAppointment checks only channel.archived = false. The channel.isPublic check that protects addAppointmentToTunnel is missing in the new-client path. The combination means: an attacker completes the bootstrap flow normally (16-bit PoW, completes in well under one second on commodity hardware, no rate limiting beyond the throttle store), receives a valid booking access token, and then submits the create-new-client payload with channelId pointing to a private (isPublic = false) channel. The booking lands as CONFIRMED if the target channel has requiresConfirmation = false (the default), otherwise as NEW. The patient-facing UI does not list private channels in its picker (/api/public/channels correctly filters isPublic = true), so the channel ID must be obtained out of band. The companion finding V-10 (schedule endpoint discloses private channels) provides exactly that: a single unauthenticated GET reveals every private channel ID for any tenant. V-10 plus V-11 together make private channels fully reachable to anonymous attackers. As of time of publication, no known patched versions are available.
CVE-2026-48076
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (24th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMmedium confidence
- EG Risk
- 60EG Risk 60/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)Severity65% × 45%The EG Score, 6.5 of 10.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 or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix. - EPSS PROB
- 0.3%
- EPSS %ILE
- 24th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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
September 8, 2026
Advisory Details (1)
Auto-updated Aug 6, 2026bootstrap booking flow allows unauthenticated booking on isPublic=false channels · Advisory · open-reception/appointment-booking-software · GitHub
https://github.com/open-reception/appointment-booking-software/security/advisories/GHSA-3658-3j75-p5j3Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 42× 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 107 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 7 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-12 16:01 UTCEG score recompute
- 2026-10-11 19:44 UTCEG score recompute
- 2026-10-11 16:58 UTCEG score recompute
- 2026-10-11 14:23 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-06 23:22 UTCEG score recompute
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-05 08:21 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-04 05:47 UTCEG score recompute
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-02 09:36 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-09-30 22:59 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-09-29 05:51 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-09-27 17:27 UTCEG score recompute
Show 75 moreShow fewer
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-09-25 04:19 UTCEG score recompute
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-09-23 13:48 UTCEG score recompute
- 2026-09-22 13:12 UTCEG score recompute
- 2026-09-21 12:43 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-09-20 10:56 UTCEG score recompute
- 2026-09-19 07:25 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-09-18 06:08 UTCEG score recompute
- 2026-09-17 05:40 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-09-15 04:30 UTCEG score recompute
- 2026-09-14 04:00 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-09-13 03:33 UTCEG score recompute
- 2026-09-12 03:05 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-09-11 02:36 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-09-10 02:08 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-07 17:50 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-06 10:07 UTCEG score recompute
- 2026-09-05 09:36 UTCEG score recompute
- 2026-09-04 09:08 UTCEG score recompute
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-03 06:11 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-01 17:42 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-31 11:59 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-30 10:56 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-29 10:28 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-28 01:22 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-27 00:53 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-26 00:25 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-24 23:45 UTCEG score recompute
- 2026-08-23 23:17 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-22 22:50 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-21 22:22 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-19 21:27 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-18 20:40 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-17 20:12 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-16 19:41 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-15 19:13 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-14 18:45 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-12 17:49 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-11 17:22 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-09 16:22 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-48076?
When was the CVE record for CVE-2026-48076 published?
Is CVE-2026-48076 actively exploited?
What is the CVSS score of CVE-2026-48076?
How do I remediate CVE-2026-48076?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-48076
Is Your Infrastructure Affected by CVE-2026-48076?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.