Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-gj7p-595x-qwf5
No affected components available
Affected Components
DSF FHIR Server with enabled OIDC authentication. DSF BPE Server with enabled OIDC authentication.
Summary
OIDC-authenticated sessions had no configured maximum inactivity timeout. Sessions persisted indefinitely after login, even after the OIDC access token expired.
Impact
If a user logs in via OIDC and leaves their browser without explicitly logging out, the session remains valid indefinitely. Another person using the same browser can access the DSF UI with the previous user's permissions. This is a realistic threat in hospital environments with shared workstations.
Only affects OIDC browser sessions, not relevant for mTLS machine-to-machine communication.
Fix (commits f4ecb00, 7d25fea)
- Added configurable session timeout via
dev.dsf.server.auth.oidc.session.timeout(default:PT30M). - Enabled
logoutWhenIdTokenIsExpired(true)in OpenID configuration to tie session lifetime to token lifetime. - Websocket sessions are now closed with
VIOLATED_POLICYwhen credentials expire, prevents stale websocket connections from continuing to receive events after session timeout.
The vulnerability requires physical access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability.
Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
- CVE-2026-40939Alias
- EUVD-2026-24493Alias
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard