Vulnerability in com.oviva.telematik:epa4all-client (CVE-2026-45575)
Summary
Vulnerability in com.oviva.telematik:epa4all-client (CVE-2026-45575). 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 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.
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-45575 has been found in com.oviva.telematik:epa4all-client.
Confidential information can be exposed externally. CVSS score: 7.4/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-45575" on the vendor's site.
CVE-2026-45575 (com.oviva.telematik:epa4all-client) — CWE-347 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.2.2 — apply immediately
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-347) exists in com.oviva.telematik:epa4all-client.
Check the vendor advisory for the affected versions of com.oviva.telematik:epa4all-client.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 1.2.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade com.oviva.telematik:epa4all-client to 1.2.2ステージング環境で 1.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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