Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-40939: CWE-613: Insufficient Session Expiration in datasharingframework dsf

0
Medium
VulnerabilityCVE-2026-40939cvecve-2026-40939cwe-613
Published: Tue Apr 21 2026 (04/21/2026, 21:07:10 UTC)
Source: CVE Database V5
Vendor/Project: datasharingframework
Product: dsf

Description

CVE-2026-40939 is a medium severity vulnerability in the Data Sharing Framework (DSF) prior to version 2. 1. 0. The issue involves insufficient session expiration for OIDC-authenticated sessions, which had no maximum inactivity timeout configured. As a result, sessions persisted indefinitely after login, even after the OIDC access token expired. This vulnerability was fixed in DSF version 2. 1. 0.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/21/2026, 21:32:12 UTC

Technical Analysis

The Data Sharing Framework (DSF) implements a distributed process engine using BPMN 2.0 and FHIR R4 standards. Versions before 2.1.0 did not enforce a maximum inactivity timeout for OIDC-authenticated sessions, allowing sessions to remain active indefinitely despite expiration of the OIDC access token. This constitutes insufficient session expiration (CWE-613). The vulnerability is addressed by configuring appropriate session timeout controls in DSF 2.1.0.

Potential Impact

Sessions remain active indefinitely after login without automatic expiration, even when the OIDC access token has expired. This could allow unauthorized continued access if session tokens are not properly invalidated, increasing the risk of session hijacking or unauthorized use. The CVSS 4.0 base score is 6.8 (medium severity), reflecting the potential for high impact on confidentiality and integrity via persistent sessions.

Mitigation Recommendations

A fix is available in Data Sharing Framework version 2.1.0, which implements proper maximum inactivity timeouts for OIDC-authenticated sessions. Users should upgrade to version 2.1.0 or later to remediate this vulnerability. No other mitigation guidance is provided or required as the issue is resolved by this official fix.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-04-15T20:40:15.518Z
Cvss Version
4.0
State
PUBLISHED
Remediation Level
null

Threat ID: 69e7e91619fe3cd2cdfaec4b

Added to database: 4/21/2026, 9:16:06 PM

Last enriched: 4/21/2026, 9:32:12 PM

Last updated: 4/22/2026, 12:00:27 AM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses