CVE-2026-48088: OpenReception authentication bypass in appointment crypto key storage

CVE-2026-48088 · Severity: critical · CVSS 9.4 · Published 2026-08-06

OpenReception is an end-to-end encrypted appointment booking platform used to manage sensitive patient and staff scheduling data. Prior to version 1.0.4, an unauthenticated attacker can register malicious encryption keys for any tenant without authorization, making themselves a co-recipient of all future appointments' encryption and enabling full decryption of patient data. This completely defeats the platform's core security promise that even administrators cannot access sensitive appointment information.

Technologies: OpenReception Appointment-Booking-Software. Vendors: OpenReception.

Quick answers

Is CVE-2026-48088 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-48088 being exploited in the wild.
How severe is CVE-2026-48088?
Critical severity, with a CVSS score of 9.4, published 6 August 2026.
Which products and versions are affected?
OpenReception Appointment-Booking-Software prior to 1.0.4.
Is there a fix for CVE-2026-48088?
A patch was published on 2026: Fixed in version 1.0.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-48088 attacked?
It is attacked over the network.
Am I affected by CVE-2026-48088?
Check whether you run OpenReception Appointment-Booking-Software at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an authentication bypass combined with weak schema validation in the `POST /api/tenants/{tenantId}/staff/{staffId}/crypto` endpoint. The handler logs an "Unauthorized crypto key storage attempt" warning when no session or registration cookie is present, then proceeds to store the attacker-controlled ML-KEM-768 public key regardless. A second bypass variant exploits the optional `email` field: when omitted alongside missing cookies, the comparison `registrationEmail === undefined` evaluates to `true`, skipping the warning log entirely. The `staff_crypto` table lacks unique constraints on `user_id`, allowing multiple attacker rows per staff ID all marked `is_active=true`. Schema validation on cryptographic fields is minimal (literal strings like `<placeholder-base64>` are accepted). The injected keys are consumed by the public appointment booking flow and used to encrypt tunnel keys via ML-KEM to all stored recipients, enabling the attacker to decrypt all appointment payloads. Version 1.0.4 patches the issue; no patches are available for earlier versions.

Affected products

  • OpenReception appointment booking software prior to 1.0.4

Timeline

  • 2026-08-06: disclosed: CVE-2026-48088 published
  • 2026: patched: Fixed in version 1.0.4

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.