CVE-2026-48021

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In epa4all, prior to version 2026-05-20, an attacker who can intercept the TLS connection between epa4all and the ePA backend can complete the VAU handshake with attacker-controlled keys and obtain the session encryption keys. All inner HTTP traffic (patient consent decisions, medication data, document operations, authorization tokens, and entitlement queries) becomes readable and modifiable. The attacker can also inject arbitrary requests through the hijacked channel. This issue has been patched in version 2026-05-20.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 24, 2026

Last Modified

July 25, 2026

Advisory Details (3)

Auto-updated Jul 24, 2026
Patch available. Sources: github, github_release.
generic

CVE-2026-48021: VAU Server Spoofing Patient-Data MITM in epa4all

https://www.machinespirits.com/advisory/aa49f0
github_release Patch Available

2026-05-20

Patch available: med-united/epa4all 2026-05-20

https://github.com/med-united/epa4all/releases/tag/2026-05-20
github Patch Available

VAU Server Authentication Bypass via Missing A_24624-01 Verification in epa4all · Advisory · med-united/epa4all · GitHub

https://github.com/med-united/epa4all/security/advisories/GHSA-vvh7-x6c7-46gh

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 13:57 UTCEG score recompute
  2. 2026-07-26 02:56 UTCEG score recompute
  3. 2026-07-25 14:18 UTCEPSS rescore
  4. 2026-07-24 18:32 UTCEG score recompute
  5. 2026-07-24 18:31 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-48021?
CVE-2026-48021 is a critical vulnerability published on July 24, 2026. In epa4all, prior to version 2026-05-20, an attacker who can intercept the TLS connection between epa4all and the ePA backend can complete the VAU handshake with attacker-controlled keys and obtain the session encryption keys. All inner HTTP traffic (patient consent decisions, medication data,…
When was CVE-2026-48021 disclosed?
CVE-2026-48021 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on July 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48021 actively exploited?
CVE-2026-48021 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-48021?
CVE-2026-48021 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-48021?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48021, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48021?

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