Vulnerability · Published Apr 21, 2026 · Assigned by GitHub_M

CVE-2026-40942DSF: Inverted Time Comparison in OIDC JWKS and Token Cache

Medium 6.3

In plain English

A medium-severity security flaw in dsf from datasharingframework. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 22% of all known vulnerabilities).

Severity (CVSS 4.0)6.3Medium
Exploit odds (30 days)0.3%top 78.2% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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 & fixed versions

EcosystemPackageFixed inAdvisory
Mavendev.dsf:dsf-bpe-process-api-v2no fix listedGHSA-xmj9-7625-f634
Mavendev.dsf:dsf-bpe-serverno fix listedGHSA-xmj9-7625-f634

Affected products (as reported)

VendorProductVersions
datasharingframework dsf < 2.1.0
dev.dsf dsf-bpe-process-api-v2 < 2.1.0
dev.dsf dsf-bpe-server < 2.1.0

Weakness: CWE-670 · Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References