Skip to content

epa4all-client: Unauthenticated REST API for Patient Record Writes

Moderate severity GitHub Reviewed Published May 19, 2026 in oviva-ag/epa4all-client • Updated Jun 4, 2026

Package

maven com.oviva.telematik:epa4all-rest-service (Maven)

Affected versions

<= 1.2.4

Patched versions

None

Description

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

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

References

@thomasrichner-oviva thomasrichner-oviva published to oviva-ag/epa4all-client May 19, 2026
Published by the National Vulnerability Database May 26, 2026
Published to the GitHub Advisory Database Jun 4, 2026
Reviewed Jun 4, 2026
Last updated Jun 4, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(6th percentile)

Weaknesses

Missing Authentication for Critical Function

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. Learn more on MITRE.

CVE ID

CVE-2026-47672

GHSA ID

GHSA-c82x-f4xr-qv33

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.