https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 21:53:36 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-321993 EUVD-2026-321993 https://cve.radiocsirt.org/vuln/euvd-2026-321993 https://cve.radiocsirt.org/vuln/fkie_cve-2026-47672 <p>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&#39;s electronic health record accessible by the institution&#39;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.</p> <p>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&#39;s electronic health record accessible by the institution&#39;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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-47672 https://cve.radiocsirt.org/vuln/ghsa-c82x-f4xr-qv33 <p><strong>Affected:</strong> Maven: com.oviva.telematik:epa4all-rest-service</p> <p>### Impact Any network-reachable caller can write arbitrary documents to any patient&#39;s electronic health record accessible by the institution&#39;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.</p> <p>### Patches - [#43](https://github.com/oviva-ag/epa4all-client/pull/43)</p> <p>### 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</p> <p>### References - MS-OVIVA-EPA4ALL-8b2af7</p> <p>### Credits [Machine Spirits](https://machinespirits.com/) ([contact@machinespirits.de](mailto:contact@machinespirits.de))</p> <p>- Dr. rer. nat. Simon Weber - Dipl.-Inf. Volker Schönefeld - Chiara Fliegner</p> <p><strong>Affected:</strong> Maven: com.oviva.telematik:epa4all-rest-service</p> <p>### Impact Any network-reachable caller can write arbitrary documents to any patient&#39;s electronic health record accessible by the institution&#39;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.</p> <p>### Patches - [#43](https://github.com/oviva-ag/epa4all-client/pull/43)</p> <p>### 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</p> <p>### References - MS-OVIVA-EPA4ALL-8b2af7</p> <p>### Credits [Machine Spirits](https://machinespirits.com/) ([contact@machinespirits.de](mailto:contact@machinespirits.de))</p> <p>- Dr. rer. nat. Simon Weber - Dipl.-Inf. Volker Schönefeld - Chiara Fliegner</p> https://cve.radiocsirt.org/vuln/ghsa-c82x-f4xr-qv33