CVE-2026-44900: CWE-295: Improper Certificate Validation in oviva-ag epa4all-client
CVE-2026-44900 is a high-severity vulnerability in oviva-ag's epa4all-client prior to version 1. 2. 1. The vulnerability arises from improper certificate validation in the SignedPublicKeysTrustValidatorImpl. isTrusted() method, where the result of the ECDSA signature verification is ignored, causing the method to accept any structurally valid signature as trusted. This flaw bypasses critical signature verification despite performing other checks like certificate chain validation and OCSP. The issue is fixed in version 1. 2. 1.
AI Analysis
Technical Summary
The epa4all-client Java component used in the Telematik Infrastruktur contained a certificate validation flaw (CWE-295) prior to version 1.2.1. Specifically, in the SignedPublicKeysTrustValidatorImpl.isTrusted() method, the boolean return value of Signature.verify() was discarded, meaning the method did not verify if the ECDSA signature actually matched. Although the method performed certificate chain validation, OCSP checks, and signature algorithm setup, it returned true for any structurally valid signature, effectively bypassing signature verification. This vulnerability allows an attacker to potentially trust forged certificates or signatures. The vulnerability is addressed in version 1.2.1.
Potential Impact
The vulnerability allows an attacker to bypass signature verification, potentially enabling acceptance of forged or malicious certificates. This can lead to compromise of confidentiality and integrity (as indicated by the CVSS vector: Confidentiality and Integrity impact are high, Availability is not affected). The vulnerability does not require privileges or user interaction and can be exploited remotely over a network. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability is fixed in epa4all-client version 1.2.1. Users should upgrade to version 1.2.1 or later to remediate the issue. Patch status is not explicitly confirmed in the vendor advisory, but the description states the issue is fixed in 1.2.1. No additional mitigations are indicated.
CVE-2026-44900: CWE-295: Improper Certificate Validation in oviva-ag epa4all-client
Description
CVE-2026-44900 is a high-severity vulnerability in oviva-ag's epa4all-client prior to version 1. 2. 1. The vulnerability arises from improper certificate validation in the SignedPublicKeysTrustValidatorImpl. isTrusted() method, where the result of the ECDSA signature verification is ignored, causing the method to accept any structurally valid signature as trusted. This flaw bypasses critical signature verification despite performing other checks like certificate chain validation and OCSP. The issue is fixed in version 1. 2. 1.
CVSS v3.1
Score 8.1high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The epa4all-client Java component used in the Telematik Infrastruktur contained a certificate validation flaw (CWE-295) prior to version 1.2.1. Specifically, in the SignedPublicKeysTrustValidatorImpl.isTrusted() method, the boolean return value of Signature.verify() was discarded, meaning the method did not verify if the ECDSA signature actually matched. Although the method performed certificate chain validation, OCSP checks, and signature algorithm setup, it returned true for any structurally valid signature, effectively bypassing signature verification. This vulnerability allows an attacker to potentially trust forged certificates or signatures. The vulnerability is addressed in version 1.2.1.
Potential Impact
The vulnerability allows an attacker to bypass signature verification, potentially enabling acceptance of forged or malicious certificates. This can lead to compromise of confidentiality and integrity (as indicated by the CVSS vector: Confidentiality and Integrity impact are high, Availability is not affected). The vulnerability does not require privileges or user interaction and can be exploited remotely over a network. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability is fixed in epa4all-client version 1.2.1. Users should upgrade to version 1.2.1 or later to remediate the issue. Patch status is not explicitly confirmed in the vendor advisory, but the description states the issue is fixed in 1.2.1. No additional mitigations are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-07T21:50:33.546Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a161539e29bf47b506c539f
Added to database: 5/26/2026, 9:48:41 PM
Last enriched: 5/26/2026, 10:04:14 PM
Last updated: 5/27/2026, 5:02:36 AM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.