CVE-2026-50576 ePA 3.x Integration: HTTP Header Injection in VAU Inner Requests
An authenticated attacker can inject CRLF characters to manipulate HTTP headers, potentially exposing patient records or bypassing authentication in ePA integrations.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-50576?
CVE-2026-50576 is a medium-severity vulnerability in fbeta-GmbH ePA3-Service-OpenSource, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-113
Which versions are affected by CVE-2026-50576?
How do I fix CVE-2026-50576?
No fix has been published for CVE-2026-50576 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-50576 being exploited?
There is no known exploitation of CVE-2026-50576 in the wild and no public exploit code.
Sources
Also known as GHSA-j8jg-7fqf-4xx9.