CVE-2026-50576
ePA 3.x Integration implements the authorization workflow and …
ePA 3.x Integration implements the authorization workflow and writes Medical Information Objects to Germany's electronic patient record. Prior to 1.3.0, ePA 3.x Integration does not neutralize CRLF characters in values used by app/vau/VAUProtokoll.py to construct VAU inner HTTP requests. The build_inner_header function interpolates the uri, host, accept_type, content_type, content_length, USER_AGENT, and insurant_id values into request lines and headers, including x-useragent and x-insurantid. An authenticated attacker who controls a value can inject additional headers into the inner request. Depending on ePA server handling, an injected x-insurantid header can expose another patient's records, and injected Authorization headers can bypass the intended authentication or authorization context. Session-derived USER_AGENT input can also poison requests across the session. This issue is fixed in version 1.3.0.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/fbeta-GmbH/ePA3-Service-OpenSource/commit/b984d15d261423302de337adae25e84c54e9c
- github.com/fbeta-GmbH/ePA3-Service-OpenSource/pull/11
- github.com/fbeta-GmbH/ePA3-Service-OpenSource/releases/tag/1.3.0
- github.com/fbeta-GmbH/ePA3-Service-OpenSource/security/advisories/GHSA-j8jg-7fqf-4xx9
- www.machinespirits.de/advisory/013a60
- nvd.nist.gov/vuln/detail/CVE-2026-50576
- cve.org/CVERecord?id=CVE-2026-50576
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.