Advisory record · GHSA-gqx7-6552-67hf

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

CVSS 7.4 HighEPSS 0.0012 · 1st percentile

Published by the GitHub Advisory Database at 15 May 2026, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.oviva.telematik:epa4all-clientMaven<1.2.21.2.2
Identifiers
GHSA-gqx7-6552-67hf · CVE-2026-45575
Weakness (CWE)
CWE-347
Published
15 May 2026
Updated
8 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of com.oviva.telematik:epa4all-client before 1.2.2 do not properly verify a cryptographic signature on the discovery document fetched from the identity provider. An attacker who can man-in-the-middle the TLS connection between the client and the IDP within the TI network can substitute a forged discovery document, causing the client to send its signed authentication material to an attacker-controlled endpoint. Upgrade to version 1.2.2. The source lists no workarounds.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.4 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0012, the 1st percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.