Skip to main content
VulnerabilityPublished

CVE-2026-50578: fbeta-GmbH ePA3-Service-OpenSource · Improper Certificate Validation

Affects fbeta-GmbH ePA3-Service-OpenSourceSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.3.0 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.3.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade ePA3-Service-OpenSource and fbeta-gmbh/ePA3-Service-OpenSource to 1.3.0.

Affected software

ProductAffectedFixed in
fbeta-GmbHePA3-Service-OpenSourceAffected
  • <1.3.0
Fixed in
  • 1.3.0
GitHubfbeta-gmbh/ePA3-Service-OpenSourcepkg:github/fbeta-gmbh/ePA3-Service-OpenSourceOther threatsAffected
  • <1.3.0
Fixed in
  • 1.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to version 1.3.0 or later, where proper TLS certificate validation is enforced. No other mitigation or temporary fix is indicated. Patch status is confirmed fixed in version 1.3.0.

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.

References

Community reviews

Loading reviews…