# CVE-2026-48021: Security feature bypass in epa4all

> Attackers can intercept TLS connections to read and modify sensitive patient data and inject requests due to missing certificate and hostname checks.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2026
- **Updated:** 25 Jul 2026
- **Also known as:** GHSA-vvh7-x6c7-46gh

## What is CVE-2026-48021?

CVE-2026-48021 is a critical vulnerability in med-united epa4all, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-48021?


## How do I fix CVE-2026-48021?

No fix has been published for CVE-2026-48021 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-48021 being exploited?

There is no known exploitation of CVE-2026-48021 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48021 and fix it if it is affected.

What it is: CVE-2026-48021 is a critical vulnerability in med-united epa4all, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48021 in the wild and no public exploit code.

Affected product: med-united epa4all. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48021/ (Markdown: https://insights.sbomify.com/CVE-2026-48021/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48021
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48021
- OSV: https://osv.dev/vulnerability/CVE-2026-48021

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48021/
Summaries are generated and may contain mistakes; the official description above is the record.