Vulnerability in com.oviva.telematik:epa4all-client (CVE-2026-45574)
Summary
Vulnerability in com.oviva.telematik:epa4all-client (CVE-2026-45574). Confidential information can be exposed externally. Mitigation: upgrade to 1.2.2 or later.
Original description
The description as published by the source.
epa4all-client is the Java Client for epa4all / ePA 3.0 in the Telematik Infrastruktur. Prior to 1.2.2, 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. This vulnerability is fixed in 1.2.2.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45574 has been found in com.oviva.telematik:epa4all-client.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade com.oviva.telematik:epa4all-client to 1.2.2 or later.
If unsure, ask your IT team or search "com.oviva.telematik:epa4all-client CVE-2026-45574" on the vendor's site.
CVE-2026-45574 (com.oviva.telematik:epa4all-client) — CWE-295 / CVSS v3 8.1
Attack vector: adjacent-network / unauthenticated / no user interaction
Patched: 1.2.2 — apply immediately
Workaround: Use the library directly instead of the REST wrapper.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-295) exists in com.oviva.telematik:epa4all-client.
Check the vendor advisory for the affected versions of com.oviva.telematik:epa4all-client.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 1.2.2.
Workaround: Use the library directly instead of the REST wrapper.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.oviva.telematik:epa4all-client を使っているサービスとバージョンを洗い出す。
-
2Apply temporary workaround mitigate
Use the library directly instead of the REST wrapper.パッチが適用されるまでの応急処置として、Use the library directly instead of the REST wrapper. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade com.oviva.telematik:epa4all-client to 1.2.2ステージング環境で 1.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com
- web github.com