CVE-2026-54342

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.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
8.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: 8.1Exploit: None knownExposed: 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 on the network path between epa4all and any backend (ePA Aktensystem, Konnektor, IDP, TSS) can present a self-signed TLS certificate and intercept the connection. For non-VAU connections (Konnektor, IDP), this allows direct read and modification of the inner traffic, including smartcard operations and OIDC authentication exchanges. For the ePA backend, the disabled TLS verification is the transport-level enabler for the VAU MITM described in GHSA-vvh7-x6c7-46gh. This issue has been patched in version 2026-05-20.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
41(Track)
EG Risk 41/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
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 24, 2026

Last Modified

July 24, 2026

Advisory Details (4)

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

CVE-2026-54342: TLS Verification Disabled Enables ePA MITM in epa4all

https://www.machinespirits.com/advisory/b98b02
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
github Patch Available

TLS Certificate Verification Disabled on CXF Transport Clients in epa4all · Advisory · med-united/epa4all · GitHub

https://github.com/med-united/epa4all/security/advisories/GHSA-296w-v8f6-3rf7

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 6× 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 14:54 UTCEPSS rescore
  2. 2026-07-26 14:12 UTCEG score recompute
  3. 2026-07-26 02:56 UTCEG score recompute
  4. 2026-07-25 14:18 UTCEPSS rescore
  5. 2026-07-24 18:32 UTCEG score recompute
  6. 2026-07-24 18:31 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54342?
CVE-2026-54342 is a high vulnerability published on July 24, 2026. In epa4all, prior to version 2026-05-20, an attacker on the network path between epa4all and any backend (ePA Aktensystem, Konnektor, IDP, TSS) can present a self-signed TLS certificate and intercept the connection. For non-VAU connections (Konnektor, IDP), this allows direct read and modification…
When was CVE-2026-54342 disclosed?
CVE-2026-54342 was first published in the National Vulnerability Database on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54342 actively exploited?
CVE-2026-54342 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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-54342?
CVE-2026-54342 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-54342?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54342, 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-54342

Explore →

Is Your Infrastructure Affected by CVE-2026-54342?

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