Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The epa4all-client Maven package, versions before 1.2.2, does not validate TLS certificates in production. An attacker on the network path between the ePA service and the Konnektor can present any certificate and intercept SOAP traffic, including patient identifiers and smart card operations. Upgrade to version 1.2.2. The source lists a workaround of calling the library directly instead of the REST wrapper.
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 |
|---|---|---|---|---|
| 8.1 | High | 3.1 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0014, the 3rd 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-5hhf-xmfx-4vvr
- OSV: GHSA-5hhf-xmfx-4vvr
- github.com/oviva-ag/epa4all-client/security/advisories/GHSA-5hhf-xmfx-4vvr
- nvd.nist.gov/vuln/detail/CVE-2026-45574
- 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