{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-50576 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-50576 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-50576 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2026-50576 in the wild and no public exploit code.\n\nAffected product: fbeta-GmbH ePA3-Service-OpenSource. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-50576/ (Markdown: https://insights.sbomify.com/CVE-2026-50576/index.md)","id":"CVE-2026-50576","markdown":"https://insights.sbomify.com/CVE-2026-50576/index.md","name":"CVE-2026-50576","record":{"aliases":["GHSA-j8jg-7fqf-4xx9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ePA 3.x Integration","requires_auth":"low_privilege","summary":"An authenticated attacker can inject CRLF characters to manipulate HTTP headers, potentially exposing patient records or bypassing authentication in ePA integrations.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-113","name":"Improper Neutralization of CRLF Sequences in HTTP Headers"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"ePA 3.x Integration: HTTP Header Injection in VAU Inner Requests","id":"CVE-2026-50576","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"ePA 3.x Integration: AES-GCM Nonce Reuse via Frozen VAU Request Counter","id":"CVE-2026-50577"},"packages":[],"prev":{"headline":"BetterDesk has a replay behavior vulnerability when devices are deleted","id":"CVE-2026-50575"},"products":["ePA3-Service-OpenSource"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["fbeta-GmbH"]},"summary":"An authenticated attacker can inject CRLF characters to manipulate HTTP headers, potentially exposing patient records or bypassing authentication in ePA integrations.","url":"https://insights.sbomify.com/CVE-2026-50576/"}