Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of com.oviva.telematik:epa4all-client before 1.2.2 do not properly verify a cryptographic signature on the discovery document fetched from the identity provider. An attacker who can man-in-the-middle the TLS connection between the client and the IDP within the TI network can substitute a forged discovery document, causing the client to send its signed authentication material to an attacker-controlled endpoint. Upgrade to version 1.2.2. The source lists no workarounds.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.4 | High | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0012, the 1st percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:20 UTC First seen by agentprime
- 31 Oct 2026, 14:20 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-gqx7-6552-67hf
- OSV: GHSA-gqx7-6552-67hf
- github.com/oviva-ag/epa4all-client/security/advisories/GHSA-gqx7-6552-67hf
- nvd.nist.gov/vuln/detail/CVE-2026-45575
- github.com/oviva-ag/epa4all-client/pull/36
- github.com/oviva-ag/epa4all-client/commit/9111d6fbb939007036a7f74b2a93bb278cb5af32
- github.com/oviva-ag/epa4all-client
- github.com/oviva-ag/epa4all-client/releases/tag/v1.2.2