Live › vulnerability › CVE-2026-75525
Go to dashboardOpenReception's appointment booking software, in versions 2.1.0 and earlier, lets an unauthenticated attacker store their own ML-KEM-768 public key under any existing staff user in any tenant. Future appointment data in that tenant is then encrypted to the attacker's key, so the attacker can read patient booking data.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Operators running OpenReception 2.1.0 or earlier that expose the booking platform to the internet or untrusted networks. The flaw is in the unauthenticated write path to the recipient directory, so deployments behind strict network access controls are less exposed. Teams not running OpenReception can skip it.
No product ranges from the sources yet.
2.1.0 or earlierEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. In versions 2.1.0 and prior, an unauthenticated attacker can store an arbitrary ML-KEM-768 public key under any existing user's identity in any tenant's staff-crypto recipient directory. The product's design guarantees that appointment data is end-to-end encrypted to staff members and that the staff recipient directory is not attacker-writable, so that even administrators and the operator cannot read patient data. This endpoint breaks that guarantee for an unauthenticated remote actor: it allows writing an arbitrary encryption recipient into the recipient directory of any tenant. The injected key receives the tunnel key of every appointment booked afterward in that tenant, because booking clients encrypt to all active staff keys. The attacker holds the corresponding secret key and is a persistent, unauthorized recipient of that key material. At time of publication, there are no publicly available patches.
This page as .md · .json · in your agent: get_signal("CVE-2026-75525")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.