CVE-2026-45575
HighCVSS 7.4Exploitation Probability (EPSS)
Low risk2th percentile - higher than 2% of all known CVEs
Summary
In the epa4all-client Java client, a MITM attacker on the TLS connection between client and IDP can substitute a forged discovery document, redirecting the client to attacker-controlled URLs. The client then encrypts the SMC-B signed challenge response with the attacker's key and sends it to the attacker.
Risk Assessment
An attacker can capture signed authentication material, enabling impersonation of the user in the ePA system.
Recommendation
Update epa4all-client to version 1.2.2 or later.
Other vulnerabilities in epa4all-client
See all- CVE-2026-45574High
The epa4all-client library (Java Client for epa4all / ePA 3.0 in Telematik Infrastruktur) prior to version 1.2.2 does not properly validate TLS certificates. 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, including patient identifiers (KVNR), SMC-B card operations, document content, and credential exchanges.
- CVE-2026-44900High
In the epa4all-client Java client, the SignedPublicKeysTrustValidatorImpl.isTrusted() method discards the boolean return value of ECDSA signature verification, always returning true for any structurally valid signature.
- CVE-2026-47672Medium
epa4all-client version 1.2.4 and earlier allows any network-reachable caller to write arbitrary documents to any patient's electronic health record using the institution's SMC-B card. In a misconfigured deployment (e.g., following the Docker example in the README), this is exploitable from the local network without credentials.
Original NVD description (English source)
epa4all-client is the Java Client for epa4all / ePA 3.0 in the Telematik Infrastruktur. Prior to 1.2.2, an attacker who can MITM the TLS connection between the client and the IDP (within the TI network) can substitute a forged discovery document. The forged document redirects uri_puk_idp_enc and uri_puk_idp_sig to attacker-controlled URLs. The client then encrypts the SMC-B-signed challenge response to the attacker's encryption key and POSTs it to the attacker's auth endpoint. This captures the signed authentication material. This vulnerability is fixed in 1.2.2.