epa4all Security Incident: Implement keystore based on Telematik TSL, implement hostname check and certificate check for lib-vau
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| med-united | epa4all | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Med-united | Epa4all |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.192% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Med-united
Med-united epa4all |
|
| Vendors & Products |
Med-united
Med-united epa4all |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In epa4all, prior to version 2026-05-20, an attacker who can intercept the TLS connection between epa4all and the ePA backend can complete the VAU handshake with attacker-controlled keys and obtain the session encryption keys. All inner HTTP traffic (patient consent decisions, medication data, document operations, authorization tokens, and entitlement queries) becomes readable and modifiable. The attacker can also inject arbitrary requests through the hijacked channel. This issue has been patched in version 2026-05-20. | |
| Title | epa4all Security Incident: Implement keystore based on Telematik TSL, implement hostname check and certificate check for lib-vau | |
| Weaknesses | CWE-295 CWE-347 |
|
| References |
| |
| Metrics |
cvssV3_1
|