Log in Start free

Vulnerability · Published May 26, 2026 · Assigned by GitHub_M

CVE-2026-45575epa4all-client: Improper Verification of Cryptographic Signature

High 7.4

In plain English

A high-severity security flaw in epa4all-client from com.oviva.telematik. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.4High
Exploit odds (30 days)0.1%top 98.3% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Mavencom.oviva.telematik:epa4all-client1.2.2GHSA-gqx7-6552-67hf

Affected products (as reported)

VendorProductVersions
oviva-ag epa4all-client < 1.2.2
com.oviva.telematik epa4all-client < 1.2.2

Weakness: CWE-347 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

References