How severe is GHSA-c82x-f4xr-qv33?

GHSA-c82x-f4xr-qv33 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-c82x-f4xr-qv33?

GHSA-c82x-f4xr-qv33 affects the following packages: com.oviva.telematik:epa4all-rest-service (Maven). Ecosystems affected: Maven.

How do I fix GHSA-c82x-f4xr-qv33?

No patched version of com.oviva.telematik:epa4all-rest-service has shipped for GHSA-c82x-f4xr-qv33 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-c82x-f4xr-qv33 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.oviva.telematik:epa4all-rest-service. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-c82x-f4xr-qv33 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-c82x-f4xr-qv33?

O3 pinpoints whether GHSA-c82x-f4xr-qv33 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-c82x-f4xr-qv33 actively exploited in the wild?

No public exploit code has been indexed for GHSA-c82x-f4xr-qv33 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-c82x-f4xr-qv33?

GHSA-c82x-f4xr-qv33 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 6th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-c82x-f4xr-qv33?

GHSA-c82x-f4xr-qv33 is classified as Missing Authentication (CWE-306). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-c82x-f4xr-qv33 published, and has it been updated?

GHSA-c82x-f4xr-qv33 was published on June 4, 2026 and was last updated on June 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-c82x-f4xr-qv33

MEDIUM

epa4all-client: Unauthenticated REST API for Patient Record Writes

Also known asCVE-2026-47672

Published

Jun 4, 2026

Updated

Jun 4, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk6th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

☕com.oviva.telematik:epa4all-rest-service

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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 ([email protected])

Dr. rer. nat. Simon Weber
Dipl.-Inf. Volker Schönefeld
Chiara Fliegner

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.oviva.telematik:epa4all-rest-service`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.oviva.telematik:epa4all-rest-service. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of com.oviva.telematik:epa4all-rest-service has shipped for GHSA-c82x-f4xr-qv33 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-c82x-f4xr-qv33 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-c82x-f4xr-qv33. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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](https://github.com/oviva-ag/epa4all-client/pull/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 corresp

O3 Security · Impact-Aware SCA

Is GHSA-c82x-f4xr-qv33 in your dependencies?

O3 detects GHSA-c82x-f4xr-qv33 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works