epa4all-client: Unauthenticated REST API for Patient Record Writes

Exploitation

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

CVSS

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

EPSS

• CVE-2026-47672: 0.16% estimated exploitation activity in the next 30 days; percentile 5.40 (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 Any network-reachable caller can write arbitrary documents to any patient's electronic health record accessible by the institution's SMC-B card. In a misconfigured deployment (e.g., following the production Docker example in the README), this is exploitable from the local network without credentials. Patches - #43 Workarounds Use network policies or proxies to enforce service-to-service authentication via e.g. mTLS. - run the service in an isolated network namespace e.g. as Kubernetes sidecar - service-mesh with corresponding policies References - MS-OVIVA-EPA4ALL-8b2af7 Credits Machine Spirits (contact@machinespirits.de) - Dr. rer. nat. Simon Weber - Dipl.-Inf. Volker Schönefeld - Chiara Fliegner

Published by the source

4 Jun 2026, 17:49 UTC

Last modified by the source

4 Jun 2026, 17:49 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c82x-f4xr-qv33

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

# Patch Next advisory brief: CVE-2026-47672

Advisory: epa4all-client: Unauthenticated REST API for Patient Record Writes
IDs: CVE-2026-47672, GHSA-c82x-f4xr-qv33
Record: https://patchnext.com/advisories/cve-2026-47672 (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: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.oviva.telematik:epa4all-rest-service: affected <= 1.2.4

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.oviva.telematik:epa4all-rest-service.
- 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-c82x-f4xr-qv33 (GitHub-reviewed advisory GHSA-c82x-f4xr-qv33 lists affected ranges: Maven com.oviva.telematik:epa4all-rest-service >=0 <=1.2.4)

Commands are suggestions: review each one before running it.