Use of a Password Hash With Insufficient Computational Effort in Mesalvo MEONA (MEONA Server and MEONA Client) for user accounts whose password was last set under a version before MEONA 2024.10. MEONA versions before 2024.10 protected stored passwords with SHA-1 (versions from October 2015) or stored them without protection (earlier versions). Since MEONA 2024.10 (June 2024) Argon2 is the default method and every password that is set or changed is stored with Argon2; passwords last set under an earlier version keep the earlier method until they are changed. An administrator could in addition select the storage method per account. A MEONA super administrator can read the stored value of such accounts in the user administration of the MEONA Client or export it through administrative database functions. Only accounts managed locally in MEONA are affected; accounts authenticated through the operating hospital's directory service (Active Directory / Entra ID) have no password stored in MEONA. In typical installations end users authenticate through the directory service and local accounts are limited to emergency and technical accounts. Exploitation requires super administrator permissions in MEONA (or direct access to the MEONA database) from within the operating hospital's network; MEONA is operated exclusively within closed hospital networks without exposure to the public Internet, and where a hospital permits remote access to that network at all, it is only through the hospital's own remote-access infrastructure (e.g. VPN) under the hospital's control. Installations in which every password has been set or changed under MEONA 2024.10 or later are not affected. Mesalvo is not aware of any exploitation outside the reported security test. This issue affects MEONA Server and MEONA Client in versions 2024.10, 2025.04 and 2026.03 (for accounts with passwords last set under earlier versions). MEONA 2025.04.24 and 2026.03.02 (planned Q4 2026) remove the legacy storage methods, require every affected account to set a new Argon2-protected password at next logon, and no longer display stored credential values in the user administration. See Mesalvo Security Advisory MSA-2026-002.
CVE-2026-0857
Score 6.0 from GitHub Security Advisory published 2026-05-20. NVD baseline CVSS 6.0; sources differ by 0.0.
- Lower severity and no public exploit yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 6.0
- EG Score
- 6.0MEDIUMmedium confidence
- EG Risk
- 27EG Risk 27/100
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 computedSeverity60% × 45%Exploitation0% × 40%Automatability0% × 15% - EPSS PROB
- 0.1%
- EPSS %ILE
- below the 1st
- KEV
- Not listed
Published
May 20, 2026
Last Modified
September 25, 2026
Advisory Details (1)
Auto-updated Jun 15, 2026Prescribing Security: Uncovering 5 CVEs in a Healthcare Application | SecCore GmbH
https://seccore.at/blog/cves-meona/Vendor Advisories for CVE-2026-0857(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 19× 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.
Showing the most recent 100 of 193 total refreshes for this CVE.
- 2026-10-09 20:06 UTCEPSS rescore
- 2026-10-08 17:11 UTCEPSS rescore
- 2026-10-07 23:47 UTCEPSS rescore
- 2026-10-06 15:17 UTCEPSS rescore
- 2026-10-05 17:42 UTCEPSS rescore
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-29 15:20 UTCEPSS rescore
- 2026-09-26 15:58 UTCEPSS rescore
- 2026-09-25 15:26 UTCGHSA enrichment
- 2026-09-25 14:39 UTCEG score recompute
- 2026-09-25 14:39 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-23 16:56 UTCEG score recompute
- 2026-08-23 16:56 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 22:55 UTCEG score recompute
- 2026-08-21 22:55 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 18:55 UTCEG score recompute
- 2026-08-20 18:55 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-17 09:54 UTCGHSA enrichment
- 2026-08-16 03:30 UTCEG score recompute
- 2026-08-16 03:30 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 02:03 UTCEG score recompute
- 2026-08-15 02:02 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 02:02 UTCEG score recompute
- 2026-08-14 02:02 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 01:32 UTCEG score recompute
- 2026-08-13 01:32 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 01:31 UTCEG score recompute
- 2026-08-12 01:31 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 01:32 UTCGHSA enrichment
- 2026-08-10 01:32 UTCGHSA enrichment
- 2026-08-09 01:32 UTCEG score recompute
- 2026-08-09 01:32 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 21:17 UTCEG score recompute
- 2026-08-07 21:17 UTCGHSA enrichment
- 2026-08-06 21:17 UTCEG score recompute
- 2026-08-06 21:17 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 21:18 UTCEG score recompute
- 2026-08-05 21:17 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-03 18:48 UTCEG score recompute
- 2026-08-03 18:48 UTCGHSA enrichment
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-02 17:45 UTCGHSA enrichment
- 2026-08-01 17:45 UTCEG score recompute
- 2026-08-01 17:45 UTCGHSA enrichment
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-26 08:15 UTCEG score recompute
- 2026-07-26 08:15 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:04 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-0857?
When was CVE-2026-0857 disclosed?
Is CVE-2026-0857 actively exploited?
What is the CVSS score of CVE-2026-0857?
How do I remediate CVE-2026-0857?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-0857
Is Your Infrastructure Affected by CVE-2026-0857?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.