CVE-2026-40939GHSA-GJ7P-595X-QWF5
DSF: Missing Session Timeout for OIDC Sessions
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.1.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- datasharingframework dsf
fixed in 2.1.0
- dev.dsf dsf-bpe-server
fixed in 2.1.0
- dev.dsf dsf-common-jetty
fixed in 2.1.0
- dev.dsf dsf-fhir-server
fixed in 2.1.0
- dev.dsf:dsf-common-jettyMaven
All versions
- dev.dsf:dsf-fhir-serverMaven
All versions
- dev.dsf:dsf-bpe-serverMaven
All versions