How severe is CVE-2026-45574?

CVE-2026-45574 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-45574?

CVE-2026-45574 affects the following packages: com.oviva.telematik:epa4all-client (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-45574?

Update com.oviva.telematik:epa4all-client to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-45574 is resolved across your whole dependency graph.

How do I detect CVE-2026-45574 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.oviva.telematik:epa4all-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-45574 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-45574 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-45574 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2026-45574 published, and has it been updated?

CVE-2026-45574 was published on May 26, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2026-45574 — epa4all-client

HIGHFix: oviva-ag/epa4all-client#36

CVE-2026-45574 is a high-severity (CVSS 8.1) vulnerability in com.oviva.telematik:epa4all-client. A fix is available for com.oviva.telematik:epa4all-client — see the affected versions and patch details below.

epa4all-client: TLS Certificate Validation Disabled in Production

Also known asGHSA-5hhf-xmfx-4vvr

Published

May 26, 2026

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 12, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕com.oviva.telematik:epa4all-client

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

An attacker on the network path between the ePA service and the Konnektor can present any TLS certificate (self-signed, expired, wrong CN) and intercept all SOAP traffic. This includes patient identifiers (KVNR), SMC-B card operations (authentication, signing), document content, and credential exchanges.

Patches

#36

Workarounds

Use the library directly instead of the REST wrapper.

Resources

MS-OVIVA-EPA4ALL-771a78

Credits

Machine Spirits ([email protected])

Dr. rer. nat. Simon Weber
Dipl.-Inf. Volker Schönefeld
Chiara Fliegner

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.oviva.telematik:epa4all-client`	all versions	1.2.2`com.oviva.telematik:epa4all-client:1.2.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.oviva.telematik:epa4all-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.oviva.telematik:epa4all-client to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-45574 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact An attacker on the network path between the ePA service and the Konnektor can present any TLS certificate (self-signed, expired, wrong CN) and intercept all SOAP traffic. This includes patient identifiers (KVNR), SMC-B card operations (authentication, signing), document content, and credential exchanges. ### Patches [#36](https://github.com/oviva-ag/epa4all-client/pull/36) ### Workarounds Use the library directly instead of the REST wrapper. ### Resources - MS-OVIVA-EPA4ALL-771a78 ### Credits [Machine Spirits](https://machinespirits.com/) ([[email protected]](mailto:cont

O3 Security · Impact-Aware SCA

Is CVE-2026-45574 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works