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.
Published: 2026-08-18
Score: 6.8 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows an authenticated attacker to inject arbitrary HTTP headers into internal requests by controlling values that are not neutralized for CRLF characters. This insertion can add headers such as x-insurantid or Authorization, potentially exposing another patient's records or bypassing authentication constraints. The injected headers are then forwarded to the ePA server, compromising confidentiality, integrity, and access control.

Affected Systems

Products from fbeta‑GmbH, specifically ePA3‑Service‑OpenSource, are affected whenever a version prior to 1.3.0 is deployed. The flaw resides in the app/vau/VAUProtokoll.py component which constructs inner HTTP requests for the electronic patient record workflow. All installations using the vulnerable code path are susceptible.

Risk and Exploitability

The CVSS score of 6.8 indicates a medium severity. The EPSS score is unavailable, and the vulnerability is not currently listed in CISA’s KEV catalog. Exploitation requires authentication and control over certain input fields that are reflected in request headers; the likely attack vector is through normal application use by a legitimate user who can supply crafted data. When exploited, it can lead to data disclosure and unauthorized access, though the extent depends on the downstream ePA server’s handling of injected headers.

Generated by OpenCVE AI on August 18, 2026 at 18:56 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the 1.3.0 update to ePA3‑Service‑OpenSource or later to eliminate the header injection bug.
  • If immediate upgrading is not possible, enforce input validation on the fields that populate inner request headers—strip CRLF sequences and reject any value containing newline characters.
  • Audit or disable features that allow session‑derived USER_AGENT or other user‑controlled data from influencing internal HTTP headers, and monitor logs for unusual header patterns.

Generated by OpenCVE AI on August 18, 2026 at 18:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 18 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 18 Aug 2026 17:00:00 +0000

Type Values Removed Values Added
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.
Title ePA 3.x Integration: HTTP Header Injection in VAU Inner Requests
Weaknesses CWE-113
References
Metrics cvssV3_1

{'score': 6.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-18T19:07:45.151Z

Reserved: 2026-06-04T21:34:34.427Z

Link: CVE-2026-50576

cve-icon Vulnrichment

Updated: 2026-08-18T19:07:42.473Z

cve-icon NVD

Status : Received

Published: 2026-08-18T17:16:58.633

Modified: 2026-08-18T20:17:16.150

Link: CVE-2026-50576

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T19:00:12Z

Weaknesses
  • CWE-113

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