# epa4all-client: Unauthenticated REST API for Patient Record Writes

Advisory record · `GHSA-c82x-f4xr-qv33`

- **Identifiers:** `GHSA-c82x-f4xr-qv33` · `CVE-2026-47672`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-306](https://cwe.mitre.org/data/definitions/306.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 4 Jun 2026
- **Updated:** 4 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Jun 2026, 17:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.oviva.telematik:epa4all-rest-service` (Maven): affected `<=1.2.4`; no fixed version yet

## Machine-written summary

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

> Versions 1.2.4 and earlier of the com.oviva.telematik:epa4all-rest-service Maven package are affected. Any network-reachable caller can write arbitrary documents to patient health records accessible through the institution's SMC-B card, and in a misconfigured deployment this needs no credentials and can be done from the local network. No fixed version is listed; the source suggests isolating the service with network policies, a service mesh, or mutual TLS between services.

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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0016, the 5th percentile, on 10 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-c82x-f4xr-qv33)

## Sources

- [GitHub Advisory Database: GHSA-c82x-f4xr-qv33](https://github.com/advisories/GHSA-c82x-f4xr-qv33)
- [OSV: GHSA-c82x-f4xr-qv33](https://osv.dev/vulnerability/GHSA-c82x-f4xr-qv33)
- <https://github.com/oviva-ag/epa4all-client/security/advisories/GHSA-c82x-f4xr-qv33>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-47672>
- <https://github.com/oviva-ag/epa4all-client/pull/43>
- <https://github.com/oviva-ag/epa4all-client>

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-c82x-f4xr-qv33>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c82x-f4xr-qv33/>. Everything for agents: <https://agentprime.io/llms.txt>.