Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-g8r3-5hwf-qp96

HIGH

GHSA-g8r3-5hwf-qp96 is a high-severity (CVSS 8.1) vulnerability in com.oviva.telematik:epa4all-client. O3 Security confirms whether GHSA-g8r3-5hwf-qp96 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

epa4all-client has a VAU Signature bypass

Also known asCVE-2026-44900
Published
May 8, 2026
Updated
Jun 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected
com.oviva.telematik:epa4all-client

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

In SignedPublicKeysTrustValidatorImpl.isTrusted(), the ECDSA signature verification at line 45 discards the boolean return value of Signature.verify(). The method performs certificate chain validation, OCSP check, and signature algorithm setup, but never checks whether the signature actually matches. For any structurally valid signature, it returns true.

Patches

Patched in #34.

Workarounds

None.

Resources

Credits

Machine Spirits ([email protected])

  • Dr. rer. nat. Simon Weber
  • Dipl.-Inf. Volker Schönefeld
  • Chiara Fliegner

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.oviva.telematik:epa4all-clientall versions1.2.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.oviva.telematik:epa4all-client. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update com.oviva.telematik:epa4all-client to 1.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g8r3-5hwf-qp96 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-g8r3-5hwf-qp96 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-g8r3-5hwf-qp96. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact In SignedPublicKeysTrustValidatorImpl.isTrusted(), the ECDSA signature verification at line 45 discards the boolean return value of Signature.verify(). The method performs certificate chain validation, OCSP check, and signature algorithm setup, but never checks whether the signature actually matches. For any structurally valid signature, it returns true. ### Patches Patched in [#34](https://github.com/oviva-ag/epa4all-client/pull/34). ### Workarounds None. ### Resources - [MS-OVIVA-EPA4ALL-d76aec](https://www.machinespirits.com/advisory/d76aec/) ### Credits [Machine Spirits](ht
O3 Security · Impact-Aware SCA

Is GHSA-g8r3-5hwf-qp96 in your dependencies?

O3 detects GHSA-g8r3-5hwf-qp96 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.