CVE-2026-50576: fbeta-GmbH ePA3-Service-OpenSource · HTTP Request/Response Splitting
Affects fbeta-GmbH ePA3-Service-OpenSourceSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium : upgrade to 1.3.0 when convenient.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.3.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade ePA3-Service-OpenSource and fbeta-gmbh/ePA3-Service-OpenSource to 1.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| fbeta-GmbHePA3-Service-OpenSource | Affected
| Fixed in
|
GitHubfbeta-gmbh/ePA3-Service-OpenSourcepkg:github/fbeta-gmbh/ePA3-Service-OpenSourceOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in version 1.3.0 of ePA3-Service-OpenSource. Users should upgrade to version 1.3.0 or later to remediate this issue. No other mitigation or temporary workaround is indicated.
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.
References
- github.com/fbeta-GmbH/ePA3-Service-OpenSource/security/advisories/GHSA-j8jg-7fqf-4xx9 (opens in a new tab)
- github.com/fbeta-GmbH/ePA3-Service-OpenSource/pull/11 (opens in a new tab)
- github.com/fbeta-GmbH/ePA3-Service-OpenSource/commit/b984d15d261423302de337adae25e84c54e9c2d1 (opens in a new tab)
- github.com/fbeta-GmbH/ePA3-Service-OpenSource/releases/tag/1.3.0 (opens in a new tab)
- machinespirits.de/advisory/013a60 (opens in a new tab)