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

CVE-2026-40942

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

DSF: Inverted Time Comparison in OIDC JWKS and Token Cache

Also known asGHSA-xmj9-7625-f634
Published
Apr 21, 2026
Updated
Aug 4, 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

The Data Sharing Framework (DSF) implements a distributed process engine based on the BPMN 2.0 and FHIR R4 standards. Prior to 2.1.0, 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. This vulnerability is fixed in 2.1.0.

Affected Packages

2 total
EcosystemPackageVulnerable rangeFix
☕Mavendev.dsf:dsf-bpe-process-api-v2all versionsNo fix
☕Mavendev.dsf:dsf-bpe-serverall versionsNo fix

Detection & mitigation playbook

Open-source dependency

  1. 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.

  2. Remediation status

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

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether CVE-2026-40942 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 CVE-2026-40942. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The Data Sharing Framework (DSF) implements a distributed process engine based on the BPMN 2.0 and FHIR R4 standards. Prior to 2.1.0, 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 th
O3 Security · Impact-Aware SCA

Is CVE-2026-40942 in your dependencies?

O3 detects CVE-2026-40942 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