CVE-2026-48079

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (42nd 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-54150 (ENISA EUVD)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.4Exploit: 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 version 1.0.2, when a user navigates to the /logout page, the page's server-side load handler deletes the access_token cookie before calling /api/auth/logout via an internal event.fetch(). The internal fetch consequently runs without the auth cookie, so apiAuthHandle rejects it, the logout handler never executes, and SessionService.revokeSession() is never called for the current session. The DB session row remains valid until its natural expiry (one week by default). The user sees a successful logout (cookie gone, UI returns to login), but any party still holding a copy of the now-deleted access token can continue making authenticated API calls until the session naturally expires. The root cause is a simple ordering mistake. The same auth subsystem implements the correct order in /api/auth/logout: revoke the current DB session first, then delete the cookie. The page-level wrapper does the opposite. Version 1.0.2 initiates server-side logout before removing authentication cookies and first appears in version 1.0.2. Version 2.0.0 later replaces this with a race-free client-side logout flow.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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.
EPSS PROB
0.5%
EPSS %ILE
42nd
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 (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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: 14 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 none (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.

The score's inputs: 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

August 6, 2026

Last Modified

October 23, 2026

Advisory Details (3)

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

logout page clears local access_token before server-side revocation, leaving duplicated tokens valid until expiry · Advisory · open-reception/appointment-booking-software · GitHub

https://github.com/open-reception/appointment-booking-software/security/advisories/GHSA-hrhm-m2hm-7cjh
GitHub commit Patch Available

commit f833dbf50059 (open-reception/appointment-booking-software)

Patch available: open-reception/appointment-booking-software v1.0.2 (contains commit f833dbf50059)

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

commit 2419f9e87a8a (open-reception/appointment-booking-software)

Patch available: open-reception/appointment-booking-software v2.0.0 (contains commit 2419f9e87a8a)

https://github.com/open-reception/appointment-booking-software/commit/2419f9e87a8abad72f31b1fedeb80c758b30322e

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× 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 138 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 38 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48079?
CVE-2026-48079 is a high-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.2, when a user navigates to the /logout page, the page's server-side load handler deletes the access_token cookie before calling /api/auth/logout via an internal…
When was the CVE record for CVE-2026-48079 published?
The CVE record for CVE-2026-48079 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-48079 actively exploited?
CVE-2026-48079 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48079?
CVE-2026-48079 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48079?
A fix for CVE-2026-48079 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-48079

Explore →

Is Your Infrastructure Affected by CVE-2026-48079?

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

Book a Demo →Browse All CVEs