CVE-2026-48075

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” 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.4% (36th 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-54144 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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: 6.5Exploit: 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.5, the add-to-tunnel endpoint creates a new appointment row in any client tunnel without any caller authentication. A request that supplies any valid tunnelId and any valid emailHash (the two need not belong to the same tunnel) results in an inserted appointment with status = "CONFIRMED", attacker-controlled ciphertext fields, attacker-controlled date and duration, and an attacker-chosen agent. The endpoint validates only that some tunnel exists with the given emailHash, then writes the appointment using the attacker-supplied tunnelId directly. The emailHash lookup is effectively an existence check on the tenant; it does not authenticate the caller as the owner of the supplied tunnelId. Combined with the absence of any session, Authorization header, booking access token, or PoW, this makes the endpoint accept arbitrary appointment writes into arbitrary tunnels. By contrast, the sibling endpoint create-new-client (used to bootstrap a brand-new client tunnel) requires a Bearer bootstrap booking access token issued by the bootstrap-challenge / bootstrap-verify flow. The add-to-tunnel endpoint, intended for return-clients booking additional appointments, has no equivalent gate. The application's own middleware confirms this is intentional: add-to-tunnel is explicitly listed in the apiAuthHandle public-route allowlist alongside the bootstrap and challenge endpoints (which legitimately have no session). Version 1.0.5 fixes the issue.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
36th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

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

October 23, 2026

Advisory Details (2)

Auto-updated Aug 6, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

unauthenticated add-to-tunnel endpoint accepts arbitrary appointment injections · Advisory · open-reception/appointment-booking-software · GitHub

https://github.com/open-reception/appointment-booking-software/security/advisories/GHSA-rhp5-vmcx-4qm8
GitHub commit Patch Available

commit 4522a44c0017 (open-reception/appointment-booking-software)

Patch available: open-reception/appointment-booking-software v1.0.5 (contains commit 4522a44c0017)

https://github.com/open-reception/appointment-booking-software/commit/4522a44c001782848faff5529d7c1e2be7ac9ef5

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 40× 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 129 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 29 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48075?
CVE-2026-48075 is a medium-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.5, the add-to-tunnel endpoint creates a new appointment row in any client tunnel without any caller authentication. A request that supplies any valid tunnelId and any…
When was the CVE record for CVE-2026-48075 published?
The CVE record for CVE-2026-48075 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-48075 actively exploited?
CVE-2026-48075 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48075?
CVE-2026-48075 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48075?
A fix for CVE-2026-48075 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-48075

Explore →

Is Your Infrastructure Affected by CVE-2026-48075?

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

Book a Demo →Browse All CVEs