CVE-2026-48080

HIGHPre-NVD 8.08.0
EchelonGraph scoreMEDIUM confidence

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

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

8.0EG
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.5%CVSS: 8.0Exploit: 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.2, the GET /api/tenants/{id} endpoint returns the full tenant record to any authenticated TENANT_ADMIN of that tenant, including the databaseUrl field. This field contains the live PostgreSQL connection string the application uses to connect to that tenant's database. In the tested official docker-compose.prod.yml deployment, the connection string contained the user postgres with rolsuper=true and the plaintext password from secrets/postgres_password.txt. Operators who configure a non-superuser PostgreSQL user via secrets/postgres_user.txt would expose a less privileged credential, but the disclosure of the connection string itself is independent of that choice. The same credential applies to every database managed by that PostgreSQL instance: the central appointment_booking database, every per-tenant database (one per tenant), and the postgres administrative database. A TENANT_ADMIN of one tenant who can reach postgres:5432 (directly via internal network, indirectly via any SSRF, RCE, or file-read in the application) can read every other tenant's appointment ciphertexts, key shares, and metadata; read the central user table, including all GLOBAL_ADMIN accounts, password hashes, and session records; modify or delete any data in any tenant database; and/or i a superuser-scoped deployment: use PostgreSQL's pg_read_server_files, COPY ... FROM PROGRAM, and CREATE EXTENSION for further escalation inside the database container. This breaks the per-tenant database isolation that is otherwise the primary cross-tenant control in the application. The application code carefully scopes most queries to the calling tenant's database, but those scopings are irrelevant once the attacker holds the credentials that bypass the application entirely. Version 1.0.2 fixes the issue.

CVSS v3
8.0
EG Score
8.0HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity80% × 45%
Impact severity (EG Severity): CVSS 8.0 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
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 (8.0): severity, escalated by confirmed exploitation. This CVE's 8.0 is its impact severity (EG Severity), not escalated.

EG Severity
8.0 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-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, Track* at medium and Attend at high mission impact.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: 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 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.

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 (2)

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

tenant detail endpoint discloses live PostgreSQL connection string, superuser-scoped in the tested official deployment · Advisory · open-reception/appointment-booking-software · GitHub

https://github.com/open-reception/appointment-booking-software/security/advisories/GHSA-v7fw-6xpm-7gj9
GitHub commit Patch Available

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

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

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48080?
CVE-2026-48080 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, the GET /api/tenants/{id} endpoint returns the full tenant record to any authenticated TENANTADMIN of that tenant, including the databaseUrl field. This field contains…
When was the CVE record for CVE-2026-48080 published?
The CVE record for CVE-2026-48080 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-48080 actively exploited?
CVE-2026-48080 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48080?
CVE-2026-48080 has a CVSS base score of 8.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48080?
A fix for CVE-2026-48080 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-48080

Explore →

Is Your Infrastructure Affected by CVE-2026-48080?

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

Book a Demo →Browse All CVEs