Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-5hhf-xmfx-4vvr | epa4all-client: TLS Certificate Validation Disabled in Production |
Wed, 27 May 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 27 May 2026 10:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Com.oviva.telematik
Com.oviva.telematik epa4all-client Oviva-ag Oviva-ag epa4all-client |
|
| Vendors & Products |
Com.oviva.telematik
Com.oviva.telematik epa4all-client Oviva-ag Oviva-ag epa4all-client |
Tue, 26 May 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | epa4all-client is the Java Client for epa4all / ePA 3.0 in the Telematik Infrastruktur. Prior to 1.2.2, an attacker on the network path between the ePA service and the Konnektor can present any TLS certificate (self-signed, expired, wrong CN) and intercept all SOAP traffic. This includes patient identifiers (KVNR), SMC-B card operations (authentication, signing), document content, and credential exchanges. This vulnerability is fixed in 1.2.2. | |
| Title | epa4all-client: TLS Certificate Validation Disabled in Production | |
| Weaknesses | CWE-295 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-27T13:21:07.023Z
Reserved: 2026-05-12T19:00:14.600Z
Link: CVE-2026-45574
Updated: 2026-05-27T13:21:03.565Z
Status : Deferred
Published: 2026-05-26T22:16:43.887
Modified: 2026-06-17T10:52:13.450
Link: CVE-2026-45574
No data.
OpenCVE Enrichment
Updated: 2026-05-27T10:08:23Z
Github GHSA