References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [email protected].

Change History

{"timestamp":"2026-07-25T00:56:57.881404Z","id":"CVE-2026-48021","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}

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.

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CWE-295

CWE-347

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

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

https://www.machinespirits.com/advisory/aa49f0

[{"vendor":"med-united","product":"epa4all","versions":[{"version":"< 2026-05-20","status":"affected"}]}]