Improper Verification of Cryptographic Signature in com.oviva.telematik:epa4all-client

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2026-45575: 0.12% estimated exploitation activity in the next 30 days; percentile 1.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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 u ripukidpenc and uripukidpsig 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. Patches #36 Workarounds None. Resources - MS-OVIVA-EPA4ALL-d453c1 Credits Machine Spirits (contact@machinespirits.de) - Dr. rer. nat. Simon Weber - Dipl.-Inf. Volker Schönefeld - Chiara Fliegner

Published by the source

15 May 2026, 18:30 UTC

Last modified by the source

8 Jun 2026, 23:31 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gqx7-6552-67hf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45575

Advisory: Improper Verification of Cryptographic Signature in com.oviva.telematik:epa4all-client
IDs: CVE-2026-45575, GHSA-gqx7-6552-67hf
Record: https://patchnext.com/advisories/cve-2026-45575 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.oviva.telematik:epa4all-client 1.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.oviva.telematik:epa4all-client: affected < 1.2.2; fixed in 1.2.2

## Suggested inspection (read-only)
- Maven com.oviva.telematik:epa4all-client: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.oviva.telematik:epa4all-client.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gqx7-6552-67hf (GitHub-reviewed advisory GHSA-gqx7-6552-67hf lists affected ranges: Maven com.oviva.telematik:epa4all-client >=0 <1.2.2)

Commands are suggestions: review each one before running it.