CVE-2026-50578

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-61056 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

ePA 3.x Integration implements the authorization workflow and writes Medical Information Objects to Germany's electronic patient record. Prior to 1.3.0, ePA 3.x Integration disables TLS certificate verification for both ePA connections in app/vau/VAUProtokoll.py and Konnektor connections in app/konnektor/Konnektor.py. A network-positioned attacker can present an arbitrary certificate, terminate the TLS connection, and intercept ePA traffic. The VAU protocol does not provide an effective fallback because its application-layer certificate validation is also broken in affected versions. The Konnektor session uses self.session.verify set to False while the client authenticates with self.session.cert, so an attacker impersonating the Konnektor can receive the client's mutual TLS certificate exchange and observe smartcard operations. This issue is fixed in version 1.3.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 18, 2026

Last Modified

October 22, 2026

Advisory Details (5)

Auto-updated Aug 18, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
Web page

Deaktivierte TLS-Zertifikatsprüfung im fbeta ePA3-Service

https://www.machinespirits.de/advisory/4b68b0
GitHub advisoryMentions a patch (unverified)

TLS Certificate Verification Universally Disabled · Advisory · fbeta-GmbH/ePA3-Service-OpenSource · GitHub

https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/security/advisories/GHSA-j9m9-pmwv-hwwr
GitHub release Patch Available

1.3.0

Patch available: fbeta-GmbH/ePA3-Service-OpenSource 1.3.0

https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/releases/tag/1.3.0
GitHub pull request Patch Available

fix: Implement Konnektor and TI truststore management with CA bundle …

Patch available: fbeta-GmbH/ePA3-Service-OpenSource 1.3.0 (PR #9 merged 2026-05-27)

https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/pull/9
GitHub commit Patch Available

commit 0d94a76aa4d5 (fbeta-GmbH/ePA3-Service-OpenSource)

Patch available: fbeta-GmbH/ePA3-Service-OpenSource 1.3.0 (contains commit 0d94a76aa4d5)

https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/commit/0d94a76aa4d57a849f0c18fb3d6d337ec2505170

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 116 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 16 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-29 11:43 UTCEG score recompute
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-25 14:22 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-22 22:26 UTCEG score recompute
  14. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-18 03:33 UTCEG score recompute
  20. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-10-17 11:39 UTCEG score recompute
  22. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
Show 75 more
  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-12 15:59 UTCEG score recompute
  3. 2026-10-11 19:42 UTCEG score recompute
  4. 2026-10-11 16:57 UTCEG score recompute
  5. 2026-10-11 14:20 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-10-06 21:39 UTCEG score recompute
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-10-06 08:22 UTCEG score recompute
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-10-05 11:42 UTCEG score recompute
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-10-03 17:38 UTCEG score recompute
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-10-02 01:28 UTCEG score recompute
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-09-30 22:34 UTCEG score recompute
  23. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-09-30 09:48 UTCEG score recompute
  25. 2026-09-28 23:28 UTCEG score recompute
  26. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  27. 2026-09-27 21:15 UTCEG score recompute
  28. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  29. 2026-09-27 07:56 UTCEG score recompute
  30. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  31. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  32. 2026-09-25 01:27 UTCEG score recompute
  33. 2026-09-23 21:55 UTCEG score recompute
  34. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-09-22 20:25 UTCEG score recompute
  36. 2026-09-22 07:36 UTCEG score recompute
  37. 2026-09-21 06:03 UTCEG score recompute
  38. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-09-20 03:31 UTCEG score recompute
  40. 2026-09-19 02:01 UTCEG score recompute
  41. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  42. 2026-09-18 00:29 UTCEG score recompute
  43. 2026-09-16 22:58 UTCEG score recompute
  44. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  45. 2026-09-16 10:10 UTCEG score recompute
  46. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  47. 2026-09-15 08:39 UTCEG score recompute
  48. 2026-09-13 18:24 UTCEG score recompute
  49. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  50. 2026-09-12 16:54 UTCEG score recompute
  51. 2026-09-11 15:22 UTCEG score recompute
  52. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  53. 2026-09-10 13:52 UTCEG score recompute
  54. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  55. 2026-09-07 23:11 UTCEG score recompute
  56. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  57. 2026-09-06 18:42 UTCEG score recompute
  58. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  59. 2026-09-05 17:11 UTCEG score recompute
  60. 2026-09-04 15:40 UTCEG score recompute
  61. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  62. 2026-09-03 00:56 UTCEG score recompute
  63. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  64. 2026-09-01 23:26 UTCEG score recompute
  65. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  66. 2026-09-01 10:41 UTCEG score recompute
  67. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  68. 2026-08-30 19:53 UTCEG score recompute
  69. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  70. 2026-08-30 07:09 UTCEG score recompute
  71. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  72. 2026-08-29 03:49 UTCEG score recompute
  73. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  74. 2026-08-27 19:44 UTCEG score recompute
  75. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 8th percentile

Frequently asked(5)

What is CVE-2026-50578?
CVE-2026-50578 is a high-severity vulnerability; its CVE record was published on August 18, 2026. ePA 3.x Integration implements the authorization workflow and writes Medical Information Objects to Germany's electronic patient record. Prior to 1.3.0, ePA 3.x Integration disables TLS certificate verification for both ePA connections in app/vau/VAUProtokoll.py and Konnektor connections in…
When was the CVE record for CVE-2026-50578 published?
The CVE record for CVE-2026-50578 was published on August 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-50578 actively exploited?
CVE-2026-50578 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50578?
CVE-2026-50578 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50578?
A fix for CVE-2026-50578 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50578?

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