Is CVE-2026-47672 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47672 being exploited in the wild.

How severe is CVE-2026-47672?

Medium severity, with a CVSS score of 6.5, published 26 May 2026.

Which products and versions are affected?

com.oviva.telematik:epa4all-rest-service (Maven) <= 1.2.4, ECOSYSTEM:introduced=0,last_affected=1.2.4; Oviva Epa4all-Rest-Service <= 1.2.4.

Is there a fix for CVE-2026-47672?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-47672 attacked?

It is attacked from the adjacent network, in a software library.

Am I affected by CVE-2026-47672?

Check whether you run com.oviva.telematik:epa4all-rest-service (Maven) or Oviva Epa4all-Rest-Service at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47672: Oviva epa4all-client missing authentication for patient record writes

Q: Is there a fix for CVE-2026-47672?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-47672 attacked?

It is attacked from the adjacent network, in a software library.

Q: Am I affected by CVE-2026-47672?

Check whether you run com.oviva.telematik:epa4all-rest-service (Maven) or Oviva Epa4all-Rest-Service at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47672 · Severity: medium · CVSS 6.5 · Published 2026-05-26

A vulnerability in the epa4all-client REST service allows unauthorized users on the same network to write data to patient electronic health records. This component is used to interface with medical record systems, and an exploit could allow an attacker to inject fraudulent medical documents or alter existing patient history. This poses a significant risk to data integrity and patient safety within healthcare environments.

Technologies: Oviva Epa4all-Rest-Service. Vendors: Maven, Oviva.

Quick answers

Is CVE-2026-47672 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47672 being exploited in the wild.
How severe is CVE-2026-47672?: Medium severity, with a CVSS score of 6.5, published 26 May 2026.
Which products and versions are affected?: com.oviva.telematik:epa4all-rest-service (Maven) <= 1.2.4, ECOSYSTEM:introduced=0,last_affected=1.2.4; Oviva Epa4all-Rest-Service <= 1.2.4.
Is there a fix for CVE-2026-47672?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-47672 attacked?: It is attacked from the adjacent network, in a software library.
Am I affected by CVE-2026-47672?: Check whether you run com.oviva.telematik:epa4all-rest-service (Maven) or Oviva Epa4all-Rest-Service at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The epa4all-client (specifically the epa4all-rest-service) suffers from missing authentication (CWE-306) for critical REST API endpoints. Any attacker reachable via the network (typically the local or adjacent network in standard deployments) can write arbitrary documents to any patient's electronic health record accessible by the institution's SMC-B card. This is particularly exploitable in deployments following the default production Docker examples which may lack external authentication layers. Attackers can achieve full integrity loss of patient records. A patch is available in the project's repository, and workarounds include implementing mTLS or isolating the service within a Kubernetes sidecar or service mesh.

Affected products

oviva-ag epa4all-rest-service <= 1.2.4

Identifiers

CVE-2026-47672
GHSA-c82x-f4xr-qv33

Timeline

2026-05-19: disclosed: Initial disclosure by Oviva AG
2026-05-26: advisory: NVD publication date
2026-06-04: advisory: GitHub Advisory Database publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.