# CVE-2026-75525: OpenReception: unauthenticated ML-KEM key injection into the staff-crypto recipient directory in any tenant


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-qc72-9fg9-h66h

## What is CVE-2026-75525?

CVE-2026-75525 is a medium-severity vulnerability in open-reception appointment-booking-software, published on 23 Oct 2026. 

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-75525?


## How do I fix CVE-2026-75525?

No fix has been published for CVE-2026-75525 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-75525 being exploited?

There is no known exploitation of CVE-2026-75525 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75525 and fix it if it is affected.

What it is: CVE-2026-75525 is a medium-severity vulnerability in open-reception appointment-booking-software, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-75525 in the wild and no public exploit code.

Affected product: open-reception appointment-booking-software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75525/ (Markdown: https://insights.sbomify.com/CVE-2026-75525/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75525
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75525
- OSV: https://osv.dev/vulnerability/CVE-2026-75525

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75525/
Summaries are generated and may contain mistakes; the official description above is the record.