CVE-2026-40942

DSF: Inverted Time Comparison in OIDC JWKS and Token Cache

Published Apr 21, 2026 CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-xmj9-7625-f634 Data Sharing Framework has an Inverted Time Comparison in OIDC JWKS and Token Cache
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Datasharingframework
Datasharingframework dsf
Dev.dsf
Dev.dsf dsf-bpe-process-api-v2
Dev.dsf dsf-bpe-server
Vendors & Products Datasharingframework
Datasharingframework dsf
Dev.dsf
Dev.dsf dsf-bpe-process-api-v2
Dev.dsf dsf-bpe-server
Type Values Removed Values Added
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.
Title DSF: Inverted Time Comparison in OIDC JWKS and Token Cache
Weaknesses CWE-670
References
Metrics cvssV4_0

{'score': 6.3, '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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Apr 22, 2026, 6:11 PM
Reserved
Apr 15, 2026, 8:40 PM
Status
Deferred
Published
Apr 21, 2026, 10:16 PM
Modified
Oct 26, 2026, 10:10 PM