# 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.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-gqx7-6552-67hf

## 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 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-45575?

2 open source packages ship an affected version, including com.oviva.telematik:epa4all-client.


| Package | Ecosystem | 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45575 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-45575 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.oviva.telematik:epa4all-client (Maven): affected all versions; fixed in 1.2.2
- com.oviva.telematik:epa4all-client (Maven): affected all versions; fixed in 1.2.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45575/ (Markdown: https://insights.sbomify.com/CVE-2026-45575/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45575
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45575
- OSV: https://osv.dev/vulnerability/CVE-2026-45575

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45575/
Summaries are generated and may contain mistakes; the official description above is the record.