CVE-2026-48086 OpenReception: Tenant admin self-promotes to GLOBAL_ADMIN
Tenant admins can self-promote to global administrators via a missing authorization check, gaining full control over all tenants and platform configuration.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-48086?
CVE-2026-48086 is a critical vulnerability in open-reception appointment-booking-software, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to version 1.0.2, a TENANT_ADMIN promotes themselves to platform-wide GLOBAL_ADMIN through a single PUT request. The role-update handler accepts the `GLOBAL_ADMIN` enum value from any tenant admin updating their own tenant's staff. No policy check enforces that "only an existing GLOBAL_ADMIN may grant GLOBAL_ADMIN", so the schema validation IS the authorization decision. After re-login, the JWT contains the new role and the formerly-tenant-scoped admin reaches every other tenant on the platform. On the hosted OpenReception service this is a scope-changed escalation: a single customer-side tenant administrator gains full platform-wide administrative control over all other tenants' configuration, users, staff records, operational metadata, and tenant lifecycle. Plaintext appointment contents remain subject to the E2E model unless chained with the staff-crypto poisoning issue (V-4) or with staff-passkey hijacking (V-1). On a single-tenant self-hosted deployment it is still a privilege escalation because TENANT_ADMIN should not be able to create new tenants, modify global configuration, or manage other administrators. The same handler also accepts updates targeted at any colleague within the tenant. A tenant admin can promote a separate collaborator account instead of themselves, leaving their own audit trail clean while the platform-wide breach happens through a separate identity. Version 1.0.2 fixes the issue.
Weakness: CWE-269
Which versions are affected by CVE-2026-48086?
How do I fix CVE-2026-48086?
No fix has been published for CVE-2026-48086 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-48086 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48086 exists.
Sources
Also known as GHSA-5qfr-7q4g-3469.