datasharingframework dsf up to 2.0.x Access Token session expiration
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in datasharingframework dsf, dsf-bpe-server, dsf-common-jetty and dsf-fhir-server up to 2.0.x. Impacted is an unknown function of the component Access Token Handler. Such manipulation leads to session expiration. This vulnerability is listed as CVE-2026-40939. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability was found in datasharingframework dsf, dsf-bpe-server, dsf-common-jetty and dsf-fhir-server up to 2.0.x. It has been rated as critical. Affected by this issue is an unknown code block of the component Access Token Handler. The manipulation with an unknown input leads to a session expiration vulnerability. Using CWE to declare the problem leads to CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." Impacted is confidentiality, integrity, and availability. CVE summarizes:
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, OIDC-authenticated sessions had no configured maximum inactivity timeout. Sessions persisted indefinitely after login, even after the OIDC access token expired. This vulnerability is fixed in 2.1.0.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-40939 since 04/15/2026. The exploitation is known to be easy. The attack may be launched remotely. There are neither technical details nor an exploit publicly available.
Upgrading to version 2.1.0 eliminates this vulnerability. Applying the patch f4ecb002f7d12642f92da6b79371ed367d0140e7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Session expirationCWE: CWE-613
CAPEC: 🔒
ATT&CK: 🔒
Physical: Yes
Local: Partially
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: dsf/dsf-bpe-server/dsf-common-jetty/dsf-fhir-server 2.1.0
Patch: f4ecb002f7d12642f92da6b79371ed367d0140e7
Timeline
04/15/2026 CVE reserved04/22/2026 Advisory disclosed
04/22/2026 VulDB entry created
04/22/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-gj7p-595x-qwf5
Status: Confirmed
CVE: CVE-2026-40939 (🔒)
GCVE (CVE): GCVE-0-2026-40939
GCVE (VulDB): GCVE-100-358748
Entry
Created: 04/22/2026 07:28Changes: 04/22/2026 07:28 (69)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.