CVE-2026-48021
Received Received - Intake

Session Hijacking in epa4all via TLS Interception

Vulnerability report for CVE-2026-48021, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-24

Last updated on: 2026-07-24

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-24
Last Modified
2026-07-24
Generated
2026-07-25
AI Q&A
2026-07-24
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
epa4all epa4all to 2026-05-20 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-295 The product does not validate, or incorrectly validates, a certificate.
CWE-347 The product does not verify, or incorrectly verifies, the cryptographic signature for data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in the epa4all software before version 2026-05-20. An attacker can intercept the TLS connection between epa4all and the ePA backend. By using attacker-controlled keys, the attacker can complete the VAU handshake and obtain session encryption keys. This allows the attacker to read and modify all inner HTTP traffic, including patient consent decisions, medication data, document operations, authorization tokens, and entitlement queries. The attacker can also inject arbitrary requests through the hijacked channel.

Detection Guidance

This vulnerability involves a man-in-the-middle attack on TLS connections between epa4all and the ePA backend. Detection requires monitoring for unexpected TLS handshake anomalies or unauthorized session key exposure. Check for unusual network traffic patterns or unexpected certificate validations. No specific commands are provided in the context.

Impact Analysis

If you use epa4all prior to version 2026-05-20, an attacker could access and modify sensitive data such as patient consent decisions, medication records, and authorization tokens. They could also perform unauthorized actions by injecting requests. This could lead to privacy breaches, data theft, or unauthorized system access.

Compliance Impact

This vulnerability likely violates GDPR and HIPAA due to unauthorized access and potential exposure of sensitive personal and medical data. GDPR requires protection of personal data, and HIPAA mandates safeguards for protected health information. A breach could result in legal penalties, fines, and reputational damage for organizations.

Mitigation Strategies

Update epa4all to version 2026-05-20 or later to patch the vulnerability. Ensure all TLS connections between epa4all and the ePA backend are properly validated and encrypted. Monitor network traffic for unauthorized TLS handshake attempts or session hijacking activities.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-48021. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart