CVE-2026-54342
ePA4all accepts self-signed TLS certs enabling MITM and credential/traffic tampering.
Is CVE-2026-54342 being exploited?
Not confirmed. CVE-2026-54342 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.13% probability of exploitation in the next 30 days.
How severe is CVE-2026-54342?
CVE-2026-54342 is rated High. 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-54342?
Yes. A fix has been recorded for CVE-2026-54342. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54342 affect?
CVE-2026-54342 affects epa4all (<2026-05-20), ePA Aktensystem, Konnektor, IDP, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54342?
Upgrade epa4all to >=2026-05-20 and re-enable/verify TLS certificate validation
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
MITM via self-signed TLS cert lets attackers read/modify backend traffic, intercept smartcard ops and OIDC auth, enabling credential theft and session tampering.
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.