CVE-2026-48021
MitM breaks VAU/TLS handshake in epa4all, exposing and allowing modification of patient data.
Is CVE-2026-48021 being exploited?
Not confirmed. CVE-2026-48021 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.
How severe is CVE-2026-48021?
CVE-2026-48021 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-48021?
Yes. A fix has been recorded for CVE-2026-48021. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-48021 affect?
CVE-2026-48021 affects epa4all < 2026-05-20, ePA backend systems using VAU/TLS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48021?
Upgrade epa4all to v2026-05-20+, rotate tokens, verify TLS/VAU configs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
MitM attacker completes VAU handshake, obtains session keys, reads/modifies patient data, steals tokens, injects arbitrary requests.
Immediate action required
- affected< 2026-05-20
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.