CVE-2026-50576

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-61054 (ENISA EUVD)Source: ENISA EUVD

6.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 18, 2026

Last Modified

October 22, 2026

Advisory Details (5)

Auto-updated Aug 18, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
Web page

CRLF-Header-Injection im fbeta ePA3-Service-OpenSource

https://www.machinespirits.de/advisory/013a60
GitHub advisoryMentions a patch (unverified)

HTTP Header Injection in VAU Inner Requests · Advisory · fbeta-GmbH/ePA3-Service-OpenSource · GitHub

https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/security/advisories/GHSA-j8jg-7fqf-4xx9
GitHub release Patch Available

1.3.0

Patch available: fbeta-GmbH/ePA3-Service-OpenSource 1.3.0

https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/releases/tag/1.3.0
GitHub pull request Patch Available

fix: Sanitize header values and validate insurant ID format in VAUKanal

Patch available: fbeta-GmbH/ePA3-Service-OpenSource 1.3.0 (PR #11 merged 2026-05-27)

https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/pull/11
GitHub commit Patch Available

commit b984d15d2614 (fbeta-GmbH/ePA3-Service-OpenSource)

Patch available: fbeta-GmbH/ePA3-Service-OpenSource 1.3.0 (contains commit b984d15d2614)

https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/commit/b984d15d261423302de337adae25e84c54e9c2d1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 127 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 27 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  5. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  6. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  8. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-10-30 12:25 UTCOSV refresh
  17. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  21. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-10-25 14:22 UTCEchelonGraph re-scored
  23. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-22 22:28 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-18 03:33 UTCEchelonGraph re-scored
  7. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-12 15:59 UTCEchelonGraph re-scored
  14. 2026-10-11 19:42 UTCEchelonGraph re-scored
  15. 2026-10-11 16:57 UTCEchelonGraph re-scored
  16. 2026-10-11 14:20 UTCEchelonGraph re-scored
  17. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-07 07:44 UTCEchelonGraph re-scored
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-06 08:22 UTCEchelonGraph re-scored
  25. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  26. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-10-03 17:38 UTCEchelonGraph re-scored
  28. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  29. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-10-02 08:29 UTCEchelonGraph re-scored
  31. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-10-01 09:08 UTCEchelonGraph re-scored
  33. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  34. 2026-09-30 09:48 UTCEchelonGraph re-scored
  35. 2026-09-29 06:39 UTCEchelonGraph re-scored
  36. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  37. 2026-09-28 07:17 UTCEchelonGraph re-scored
  38. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  39. 2026-09-27 07:56 UTCEchelonGraph re-scored
  40. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  41. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  42. 2026-09-25 01:27 UTCEchelonGraph re-scored
  43. 2026-09-23 20:20 UTCEchelonGraph re-scored
  44. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  45. 2026-09-22 20:25 UTCEchelonGraph re-scored
  46. 2026-09-20 20:33 UTCEchelonGraph re-scored
  47. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  48. 2026-09-19 21:12 UTCEchelonGraph re-scored
  49. 2026-09-18 21:51 UTCEchelonGraph re-scored
  50. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  51. 2026-09-17 21:51 UTCEchelonGraph re-scored
  52. 2026-09-16 21:56 UTCEchelonGraph re-scored
  53. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  54. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  55. 2026-09-15 21:42 UTCEchelonGraph re-scored
  56. 2026-09-13 22:41 UTCEchelonGraph re-scored
  57. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  58. 2026-09-12 23:20 UTCEchelonGraph re-scored
  59. 2026-09-11 23:59 UTCEchelonGraph re-scored
  60. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  61. 2026-09-11 00:38 UTCEchelonGraph re-scored
  62. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  63. 2026-09-10 01:06 UTCEchelonGraph re-scored
  64. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  65. 2026-09-07 22:31 UTCEchelonGraph re-scored
  66. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  67. 2026-09-06 23:09 UTCEchelonGraph re-scored
  68. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  69. 2026-09-05 23:39 UTCEchelonGraph re-scored
  70. 2026-09-05 00:18 UTCEchelonGraph re-scored
  71. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  72. 2026-09-03 01:23 UTCEchelonGraph re-scored
  73. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  74. 2026-09-02 01:45 UTCEchelonGraph re-scored
  75. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile

Frequently asked(5)

What is CVE-2026-50576?
CVE-2026-50576 is a medium-severity vulnerability; its CVE record was published on August 18, 2026. 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…
When was the CVE record for CVE-2026-50576 published?
The CVE record for CVE-2026-50576 was published on August 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-50576 actively exploited?
CVE-2026-50576 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50576?
CVE-2026-50576 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50576?
A fix for CVE-2026-50576 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-50576

Explore →

Is Your Infrastructure Affected by CVE-2026-50576?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.