# CVE-2026-111312: OpenHealth through 0.2.0 Missing Authentication via /api/health-data/[id] Route

> Unauthenticated attackers can read, modify, or delete other users' medical records by accessing specific API endpoints without proper authorization checks.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-hf94-g3wx-3vc6

## What is CVE-2026-111312?

CVE-2026-111312 is a critical missing authorization vulnerability in OpenHealthForAll OpenHealth, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenHealth through 0.2.0 contains a missing authentication and authorization vulnerability in the /api/health-data/[id] GET, PATCH and DELETE handlers that query records by id without session or authorId checks. Unauthenticated attackers who know a HealthData record id can read another user's medical record data and file metadata, overwrite it with arbitrary JSON, or delete it.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-111312 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111312 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111312 is a critical missing authorization vulnerability in OpenHealthForAll OpenHealth, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111312 exists.

Affected product: OpenHealthForAll OpenHealth. 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-111312/ (Markdown: https://insights.sbomify.com/CVE-2026-111312/index.md)
```

## Sources

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

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