How severe is GHSA-xmj9-7625-f634?

No CVSS score has been assigned to GHSA-xmj9-7625-f634 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xmj9-7625-f634?

GHSA-xmj9-7625-f634 affects the following packages: dev.dsf:dsf-bpe-process-api-v2 (Maven), dev.dsf:dsf-bpe-server (Maven). Ecosystems affected: Maven.

How do I fix GHSA-xmj9-7625-f634?

No patched version of dev.dsf:dsf-bpe-process-api-v2 has shipped for GHSA-xmj9-7625-f634 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-xmj9-7625-f634 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dev.dsf:dsf-bpe-process-api-v2. 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.

How do I mitigate GHSA-xmj9-7625-f634 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.

How does O3 Security protect against GHSA-xmj9-7625-f634?

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

Is GHSA-xmj9-7625-f634 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xmj9-7625-f634 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 type of vulnerability is GHSA-xmj9-7625-f634?

GHSA-xmj9-7625-f634 is classified as CWE-670 (CWE-670). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xmj9-7625-f634 published, and has it been updated?

GHSA-xmj9-7625-f634 was published on April 15, 2026 and was last updated on May 5, 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

GHSA-xmj9-7625-f634

GHSA-xmj9-7625-f634 is a CWE-670 vulnerability in dev.dsf:dsf-bpe-process-api-v2. O3 Security confirms whether GHSA-xmj9-7625-f634 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Data Sharing Framework has an Inverted Time Comparison in OIDC JWKS and Token Cache

Also known asCVE-2026-40942

Published

Apr 15, 2026

Updated

May 5, 2026

Affected

2 pkgs

Patched

None yet

Exploits

None indexed

Blast Radius

2 pkgs affected

☕dev.dsf:dsf-bpe-process-api-v2☕dev.dsf:dsf-bpe-server

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

Affected Components

DSF FHIR Server with enabled bearer-token authentication or back-channel logout.
DSF BPE Server with enabled bearer-token authentication or back-channel logout.
DSF BPE Server API v2 process plugins using FHIR client connections with configured OIDC authentication.

Summary

The OIDC JWKS and Metadata Document caches used an inverted time comparison (isBefore instead of isAfter), causing the cache to never return cached values. Every incoming request triggered a fresh HTTP fetch of the OIDC Metadata Document and JWKS keys from the OIDC provider.
The OIDC token cache for the FHIR client connections used an inverted time comparison (isBefore instead of isAfter), causing the cache to never invalidate. Every incoming request returned the same OIDC token even if expired.

Impact

Performance: Every OIDC-authenticated request added network round-trips to the OIDC provider, increasing latency
Reliability: Cached OIDC tokens become unusable after expiration and can only be invalidated by restart of the BPE. If the OIDC provider is temporarily unreachable, all requests fail immediately instead of using cached keys
Load: Unnecessary load on the OIDC provider, potentially causing rate limiting

Fix (commits 31c2e974d, d3ca59b4d)

Fixed cache timeout comparison from isBefore to isAfter in BaseOidcClientWithCache (configuration and JWKS caches) and OidcClientWithCache (configuration, JWKS, and access token caches)
Added configurable cache timeouts via dev.dsf.server.auth.oidc.provider.client.cache.timeout.configuration.resource and dev.dsf.server.auth.oidc.provider.client.cache.timeout.jwks.resource (default: PT1H)

Affected Packages

2 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`dev.dsf:dsf-bpe-process-api-v2`	all versions	No fix
☕Maven	`dev.dsf:dsf-bpe-server`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dev.dsf:dsf-bpe-process-api-v2. 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.
Remediation status
No patched version of dev.dsf:dsf-bpe-process-api-v2 has shipped for GHSA-xmj9-7625-f634 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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.
How O3 protects you
O3 pinpoints whether GHSA-xmj9-7625-f634 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-xmj9-7625-f634. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Affected Components - DSF FHIR Server with enabled [bearer-token authentication](https://dsf.dev/operations/v2.1.0/fhir/oidc.html) or [back-channel logout](https://dsf.dev/operations/v2.1.0/fhir/oidc.html). - DSF BPE Server with enabled [bearer-token authentication](https://dsf.dev/operations/v2.1.0/bpe/oidc.html) or [back-channel logout](https://dsf.dev/operations/v2.1.0/bpe/oidc.html). - DSF BPE Server API v2 process plugins using [FHIR client connections](https://dsf.dev/operations/v2.1.0/bpe/fhir-client-connections.html) with configured OIDC authentication. ### Summary - The OIDC JWKS

O3 Security · Impact-Aware SCA

Is GHSA-xmj9-7625-f634 in your dependencies?

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

Scan my dependencies How O3 SCA works