CVE-2026-50576

Published: Ago 18, 2026 Last Modified: Ago 18, 2026
ExploitDB:
Other exploit source:
Google Dorks:
MEDIUM 6,8
Attack Vector: network
Attack Complexity: high
Privileges Required: low
User Interaction: none
Scope: unchanged
Confidentiality: high
Integrity: high
Availability: none

Description

AI Translation Available

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.

113

Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')

Incomplete
Common Consequences
Security Scopes Affected:
Integrity Access Control
Potential Impacts:
Modify Application Data Gain Privileges Or Assume Identity
Applicable Platforms
Technologies: Web Based, Web Server
View CWE Details
https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/commit/b984d15d261423302d…
https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/pull/11
https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/releases/tag/1.3.0
https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/security/advisories/GHSA-…
https://www.machinespirits.de/advisory/013a60