OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0, the session expiration check in library/auth.inc.php runs only when skip_timeout_reset is not present in the request. When skip_timeout_reset=1 is sent, the entire block that calls SessionTracker::isSessionExpired() and forces logout on timeout is skipped. As a result, any request that includes this parameter (e.g. from auto-refresh pages like the Patient Flow Board) never runs the expiration check: expired sessions can continue to access data indefinitely, abandoned workstations stay active, and an attacker with a stolen session cookie can keep sending skip_timeout_reset=1 to avoid being logged out. Version 8.0.0 fixes the issue.
CVE-2026-25476
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(low)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 24%
- KEV
- Not listed
Published
February 25, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/openemr/openemr/commit/02a6a7793402b10356a94626d78e0e1069e92a77
- security-advisories@githubhttps://github.com/openemr/openemr/security/advisories/GHSA-gx7q-6fhr-5h33
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/openemr/openemr/security/advisories/GHSA-gx7q-6fhr-5h33
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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.
- 2026-07-27 14:04 UTCEG score recompute
- 2026-07-27 13:57 UTCOSV refresh
Related CVEs(same CWE)
Same CWE
10 shownCWE-613
Frequently asked(5)
What is CVE-2026-25476?
When was CVE-2026-25476 disclosed?
Is CVE-2026-25476 actively exploited?
What is the CVSS score of CVE-2026-25476?
How do I remediate CVE-2026-25476?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-25476
Is Your Infrastructure Affected by CVE-2026-25476?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.