CVE-2026-47672 epa4all-client: Unauthenticated REST API for Patient Record Writes
Attackers can write arbitrary documents to patient health records via an unauthenticated REST API in misconfigured deployments.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-47672?
CVE-2026-47672 is a medium-severity missing authorization vulnerability in oviva-ag epa4all-client, published on 26 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
epa4all-client is the Java Client for epa4all / ePA 3.0 in the Telematik Infrastruktur. In 1.2.4 and earlier, 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.
Weakness: CWE-306
Which versions are affected by CVE-2026-47672?
2 open source packages ship an affected version, including com.oviva.telematik:epa4all-rest-service.
| Package | Affected | Fixed in |
|---|---|---|
com.oviva.telematik:epa4all-rest-service Maven | All versions to 1.2.4 | None |
com.oviva.telematik:epa4all-rest-service Maven | All versions to 1.2.4 | None |
How do I fix CVE-2026-47672?
No fix has been published for CVE-2026-47672 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-47672 being exploited?
There is no known exploitation of CVE-2026-47672 in the wild and no public exploit code.
Sources
Also known as GHSA-c82x-f4xr-qv33.