CVE-2026-45575 epa4all-client: Improper Verification of Cryptographic Signature
A man-in-the-middle attacker can bypass cryptographic signature verification to capture signed authentication material from the epa4all Java client.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-45575?
CVE-2026-45575 is a high-severity vulnerability in com.oviva.telematik epa4all-client, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-347
Which versions are affected by CVE-2026-45575?
2 open source packages ship an affected version, including com.oviva.telematik:epa4all-client.
| Package | Affected | Fixed in |
|---|---|---|
com.oviva.telematik:epa4all-client Maven | All versions | 1.2.2 |
com.oviva.telematik:epa4all-client Maven | All versions | 1.2.2 |
How do I fix CVE-2026-45575?
Upgrade com.oviva.telematik:epa4all-client to 1.2.2 or later.
Is CVE-2026-45575 being exploited?
There is no known exploitation of CVE-2026-45575 in the wild and no public exploit code.
Sources
Also known as GHSA-gqx7-6552-67hf.