CVE-2026-52723: fbeta-GmbH ePA3-Service-OpenSource · Improper Certificate Validation
Affects fbeta-GmbH ePA3-Service-OpenSourceSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.3.0 as a priority.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% 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:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| fbeta-GmbHePA3-Service-OpenSource | Affected
| Fixed in
|
GitHubfbeta-gmbh/ePA3-Service-OpenSourcepkg:github/fbeta-gmbh/ePA3-Service-OpenSourceOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in version 1.3.0 of ePA3-Service-OpenSource. Users should upgrade to version 1.3.0 or later to remediate the issue. No vendor advisory is provided to indicate alternative mitigations or temporary fixes.
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 performs VAU server certificate validation in app/vau/VAUProtokoll.py without anchoring the signed_vau_server_pub_keys and AUT_VAU_CertData certificate path to independent trusted material. A network-positioned attacker between the DiGA backend and the ePA system can intercept the VAU handshake, supply attacker-controlled certificate and key material, and satisfy the circular trust relationship. Because TLS certificate verification is also disabled in affected versions, no independent server-authentication layer prevents the attack. The attacker can impersonate the VAU server, control the negotiated session keys, and read or modify all encrypted VAU traffic. This issue is fixed in version 1.3.0.
References
- github.com/fbeta-GmbH/ePA3-Service-OpenSource/security/advisories/GHSA-q2jw-6c4w-86jc (opens in a new tab)
- github.com/fbeta-GmbH/ePA3-Service-OpenSource/pull/12 (opens in a new tab)
- github.com/fbeta-GmbH/ePA3-Service-OpenSource/commit/197c8c7fc41675f19c7f448696a2bc63fab9db5b (opens in a new tab)
- github.com/fbeta-GmbH/ePA3-Service-OpenSource/releases/tag/1.3.0 (opens in a new tab)
- machinespirits.de/advisory/a1da93 (opens in a new tab)