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

Advisory record · `GHSA-gqx7-6552-67hf`

- **Identifiers:** `GHSA-gqx7-6552-67hf` · `CVE-2026-45575`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-347](https://cwe.mitre.org/data/definitions/347.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 15 May 2026
- **Updated:** 8 Jun 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `com.oviva.telematik:epa4all-client` (Maven): affected `<1.2.2`; fixed in `1.2.2`

## 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

- 7.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 1st percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-gqx7-6552-67hf)

## Sources

- [GitHub Advisory Database: GHSA-gqx7-6552-67hf](https://github.com/advisories/GHSA-gqx7-6552-67hf)
- [OSV: GHSA-gqx7-6552-67hf](https://osv.dev/vulnerability/GHSA-gqx7-6552-67hf)
- <https://github.com/oviva-ag/epa4all-client/security/advisories/GHSA-gqx7-6552-67hf>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-45575>
- <https://github.com/oviva-ag/epa4all-client/pull/36>
- <https://github.com/oviva-ag/epa4all-client/commit/9111d6fbb939007036a7f74b2a93bb278cb5af32>
- <https://github.com/oviva-ag/epa4all-client>
- <https://github.com/oviva-ag/epa4all-client/releases/tag/v1.2.2>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-gqx7-6552-67hf>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gqx7-6552-67hf/>. Everything for agents: <https://agentprime.io/llms.txt>.