Back to CVE records
High 7.4Published May 26, 2026

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

Updated under an hour ago ()

Does this affect you?

It affects oviva-ag epa4all-client and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
7.4 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness (CWE)
CWE-347
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Deferred
Record last updated
May 28, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
oviva-ag epa4all-client
oviva:epa4all_client (from the name)
before 1.2.2
CNA record
com.oviva.telematik epa4all-client
com.oviva.telematik:epa4all_client (from the name)
before 1.2.2
CNA record

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.