# CVE-2026-54342: TLS Certificate Verification Disabled on CXF Transport Clients in epa4all

> Attackers can intercept network traffic and modify data by exploiting disabled TLS certificate verification in epa4all transport clients.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2026
- **Updated:** 27 Jul 2026

## What is CVE-2026-54342?

CVE-2026-54342 is a high-severity vulnerability in med-united epa4all, published on 24 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2026-54342 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54342 is a high-severity vulnerability in med-united epa4all, published on 24 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54342 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-54342/ (Markdown: https://insights.sbomify.com/CVE-2026-54342/index.md)
```

## Sources

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

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