How severe is GHSA-gqx7-6552-67hf?

GHSA-gqx7-6552-67hf has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-gqx7-6552-67hf?

GHSA-gqx7-6552-67hf affects the following packages: com.oviva.telematik:epa4all-client (Maven). Ecosystems affected: Maven.

How do I fix GHSA-gqx7-6552-67hf?

Update com.oviva.telematik:epa4all-client to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gqx7-6552-67hf is resolved across your whole dependency graph.

How do I detect GHSA-gqx7-6552-67hf in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.oviva.telematik:epa4all-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-gqx7-6552-67hf if there is no patch (or I can't update yet)?

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.

Is GHSA-gqx7-6552-67hf actively exploited in the wild?

No public exploit code has been indexed for GHSA-gqx7-6552-67hf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-gqx7-6552-67hf?

GHSA-gqx7-6552-67hf has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 4th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-gqx7-6552-67hf?

GHSA-gqx7-6552-67hf is classified as CWE-347 (CWE-347). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gqx7-6552-67hf published, and has it been updated?

GHSA-gqx7-6552-67hf was published on May 15, 2026 and was last updated on June 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

GHSA-gqx7-6552-67hf — epa4all-client

HIGHFix: oviva-ag/epa4all-client#36

GHSA-gqx7-6552-67hf is a high-severity (CVSS 7.4) CWE-347 vulnerability in com.oviva.telematik:epa4all-client. A fix is available for com.oviva.telematik:epa4all-client — see the affected versions and patch details below.

Improper Verification of Cryptographic Signature in com.oviva.telematik:epa4all-client

Also known asCVE-2026-45575

Published

May 15, 2026

Updated

Jun 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-gqx7-6552-67hf.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs4th percentile — riskier than 4% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-gqx7-6552-67hf by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 247,569 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

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

An attacker who can MITM the TLS connection between the client and the IDP (within the TI network) can substitute a forged discovery document. The forged document redirects u ri_puk_idp_enc and uri_puk_idp_sig to attacker-controlled URLs. The client then encrypts the SMC-B-signed challenge response to the attacker's encryption key and POSTs it to the attacker's auth endpoint. This captures the signed authentication material.

Patches

#36

Workarounds

None.

Resources

MS-OVIVA-EPA4ALL-d453c1

Credits

Machine Spirits ([email protected])

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.oviva.telematik:epa4all-client`	all versions	1.2.2`com.oviva.telematik:epa4all-client:1.2.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.oviva.telematik:epa4all-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.oviva.telematik:epa4all-client to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gqx7-6552-67hf is resolved across your whole dependency graph.
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.

Frequently Asked Questions

### Impact An attacker who can MITM the TLS connection between the client and the IDP (within the TI network) can substitute a forged discovery document. The forged document redirects u ri_puk_idp_enc and uri_puk_idp_sig to attacker-controlled URLs. The client then encrypts the SMC-B-signed challenge response to the attacker's encryption key and POSTs it to the attacker's auth endpoint. This captures the signed authentication material. ### Patches [#36](https://github.com/oviva-ag/epa4all-client/pull/36) ### Workarounds None. ### Resources - MS-OVIVA-EPA4ALL-d453c1 ### Credits [Machine Spi