← Back
CVE-2026-45574
high
CVSS 8.1
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-295) exists in com.oviva.telematik:epa4all-client.
📍 Affected scope
com.oviva.telematik:epa4all-client — .
🔥 Severity
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.2.2**.
🛡️ Workaround
Workaround: Use the library directly instead of the REST wrapper.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'com.oviva.telematik:epa4all-client' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'com.oviva.telematik:epa4all-client' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `com.oviva.telematik:epa4all-client` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Use the library directly instead of the REST wrapper.パッチが適用されるまでの応急処置として、Use the library directly instead of the REST wrapper. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade com.oviva.telematik:epa4all-client to 1.2.2ステージング環境で 1.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
com.oviva.telematik:epa4all-client
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-45574
- package https://github.com/oviva-ag/epa4all-client
- web https://github.com/oviva-ag/epa4all-client/security/advisories/GHSA-5hhf-xmfx-4vvr
- web https://github.com/oviva-ag/epa4all-client/pull/36
- web https://github.com/oviva-ag/epa4all-client/commit/9111d6fbb939007036a7f74b2a93bb278cb5af32
- web https://github.com/oviva-ag/epa4all-client/releases/tag/v1.2.2
- web https://github.com/advisories/GHSA-5hhf-xmfx-4vvr