CVE-2026-50578 ePA 3.x Integration: TLS Certificate Verification Universally Disabled
An attacker can intercept ePA traffic and observe smartcard operations by bypassing disabled TLS certificate verification in the integration library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-50578?
CVE-2026-50578 is a high-severity vulnerability in fbeta-GmbH ePA3-Service-OpenSource, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-295
Which versions are affected by CVE-2026-50578?
How do I fix CVE-2026-50578?
No fix has been published for CVE-2026-50578 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-50578 being exploited?
There is no known exploitation of CVE-2026-50578 in the wild and no public exploit code.
Sources
Also known as GHSA-j9m9-pmwv-hwwr.