---
id: CVE-2026-50578
title: >-
  ePA 3.x Integration implements the authorization workflow and writes Medical
  Information Objects to Germany's electronic patient record
summary: >-
  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 i…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'
cwe:
  - CWE-295
published: '2026-08-18'
updated: '2026-09-08'
sourceUpdated: '2026-09-08T21:02:26.047'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-50578'
references:
  - url: >-
      https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/commit/0d94a76aa4d57a849f0c18fb3d6d337ec2505170
    label: security-advisories@github.com
  - url: 'https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/pull/9'
    label: security-advisories@github.com
  - url: 'https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/releases/tag/1.3.0'
    label: security-advisories@github.com
  - url: >-
      https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/security/advisories/GHSA-j9m9-pmwv-hwwr
    label: security-advisories@github.com
  - url: 'https://www.machinespirits.de/advisory/4b68b0'
    label: security-advisories@github.com
tags:
  - nvd
epss: 0.0031
epssPercentile: 0.21271
ingestedAt: '2026-09-08T21:11:12.282Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.