CVE-2026-25164

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0, the REST API route table in apis/routes/_rest_routes_standard.inc.php does not call RestConfig::request_authorization_check() for the document and insurance routes. Other patient routes in the same file (e.g. encounters, patients/med) call it with the appropriate ACL. As a result, any valid API bearer token can access or modify every patient's documents and insurance data, regardless of the token’s OpenEMR ACLs—effectively exposing all document and insurance PHI to any authenticated API client. Version 8.0.0 patches the issue.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

February 25, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 2, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github Patch Available🟡 PoC Available

Document and Insurance REST Endpoints Skip ACL · Advisory · openemr/openemr · GitHub

https://github.com/openemr/openemr/security/advisories/GHSA-f64c-h2gh-g3f9
github_commit Patch Available

commit c5e1c4477415 (openemr/openemr)

Patch available: openemr/openemr v8_0_0_2 (contains commit c5e1c4477415)

https://github.com/openemr/openemr/commit/c5e1c44774156cd0d04f4e08ed6a81fe76d38e92

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 13:02 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-31 16:34 UTCOSV refresh
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 33 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 09:00 UTCEG score recompute
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 01:00 UTCEG score recompute
  10. 2026-08-12 13:50 UTCEPSS rescore
  11. 2026-08-11 23:55 UTCEG score recompute
  12. 2026-08-11 13:42 UTCEPSS rescore
  13. 2026-08-11 06:21 UTCEG score recompute
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-09 20:36 UTCEG score recompute
  16. 2026-08-09 13:46 UTCEPSS rescore
  17. 2026-08-09 08:38 UTCEG score recompute
  18. 2026-08-08 16:37 UTCEPSS rescore
  19. 2026-08-07 20:41 UTCEG score recompute
  20. 2026-08-06 13:46 UTCEPSS rescore
  21. 2026-08-06 03:00 UTCEG score recompute
  22. 2026-08-05 19:17 UTCEPSS rescore
  23. 2026-08-04 15:10 UTCEPSS rescore
  24. 2026-08-04 05:49 UTCEG score recompute
  25. 2026-08-03 10:36 UTCEPSS rescore
  26. 2026-08-02 19:32 UTCEG score recompute
  27. 2026-08-02 02:26 UTCEPSS rescore
  28. 2026-08-01 04:16 UTCEPSS rescore
  29. 2026-07-30 16:27 UTCEPSS rescore
  30. 2026-07-30 01:30 UTCEPSS rescore
  31. 2026-07-27 14:13 UTCEPSS rescore
  32. 2026-07-27 14:04 UTCEG score recompute
  33. 2026-07-27 13:57 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-25164?
CVE-2026-25164 is a high vulnerability published on February 25, 2026. OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0, the REST API route table in apis/routes/restroutesstandard.inc.php does not call RestConfig::requestauthorization_check() for the document and insurance routes. Other…
When was CVE-2026-25164 disclosed?
CVE-2026-25164 was first published in the National Vulnerability Database on February 25, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25164 actively exploited?
CVE-2026-25164 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.0% of all scored CVEs.
What is the CVSS score of CVE-2026-25164?
CVE-2026-25164 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-25164?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25164, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-25164

Explore →

Is Your Infrastructure Affected by CVE-2026-25164?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs