What is the CVSS score of CVE-2026-25146?

CVE-2026-25146 has a CVSS 3.1 base score of 9.6 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-25146?

Yes, a public proof-of-concept exploit is available for CVE-2026-25146. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-25146?

Within 24 hours: Identify all OpenEMR instances and their versions; if running 5.0.2-7.x, immediately rotate the gateway_api_key and review access logs for unauthorized API activity. Within 7 days: Upgrade all affected systems to OpenEMR 8.0.0 or later and regenerate all API credentials. Within 30 days: Conduct a comprehensive security audit of API access, verify no PHI was accessed, and document findings for compliance reporting.

Openemr CVE-2026-25146

CRITICAL

Information Exposure (CWE-200)

2026-03-03 security-advisories@github.com

Information Disclosure Openemr Open Emr

9.6

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Authenticate as low-privileged user
Exploit

Access gateway_api_key exposure points
Execution

Capture plaintext secret in HTTP response
Impact

Use key for unauthorized payment gateway transactions

Vulnerability Assessment

Weakness	CWE CWE-200 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V14 - Data Protection Data exposure prevention MITRE ATT&CK 2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	OpenEMR versions 5.0.2 through 7.x with payment gateway integration enabled. Requires valid user account with any privilege level to access endpoints rendering gateway_api_key in plaintext responses.
Impact	CVSS 9.6. PHI exposure.
Exploit ScenarioDerived	Access sensitive patient data without authorization.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Information disclosure in OpenEMR 5.0.2 to before 8.0.0 exposes sensitive data. PoC and patch available.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 22:05 CVSS 9.6

Sensitive data exposure in OpenEMR.

RemediationAI

Update to 8.0.0.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-200.

Know when Openemr gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 9.6 CRITICAL

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

PoC Detected

Mar 04, 2026 - 21:56 vuln.today

Public exploit code

Patch released

Mar 04, 2026 - 21:56 nvd

Patch available

CVE Published

Mar 03, 2026 - 22:16 nvd

CRITICAL 9.6

DescriptionGitHub Advisory

OpenEMR is a free and open source electronic health records and medical practice management application. From 5.0.2 to before 8.0.0, there are (at least) two paths where the gateway_api_key secret value is rendered to the client in plaintext. These secret keys being leaked could result in arbitrary money movement or broad account takeover of payment gateway APIs. This vulnerability is fixed in 8.0.0.

Executive ViewAI

Why It Matters

OpenEMR installations (versions 5.0.2 through 7.x) expose critical API gateway secrets in plaintext to clients, allowing attackers to compromise patient data and system integrations. Any organization using affected OpenEMR versions faces immediate risk of unauthorized access to protected health information (PHI) and potential HIPAA violations.

Business Impact: Severe

Compensating Controls

Apply vendor patch. If immediate patching is not feasible: (1) Restrict network access to OpenEMR administrative interfaces using firewall rules; (2) disable gateway API functionality until patched; (3) implement WAF rules to block suspicious API requests; (4) rotate gateway_api_key immediately and monitor for unauthorized usage; (5) enable comprehensive logging and alerting on all API activities.

Threat Intelligence Overview

EPSS Score

0.0%

Top 85% exploitable

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

CRITICAL severity + public POC available

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Out-of-Cycle

Exploitation· derived

Poc

System Exposure· derived

Open

Automatable· derived

Human Impact

Very High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +48

PoC: +20

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.