CVE-2026-40942: CWE-670: Always-Incorrect Control Flow Implementation in datasharingframework dsf
CVE-2026-40942 affects the Data Sharing Framework (DSF) versions prior to 2. 1. 0. The vulnerability arises from incorrect time comparison logic in caching mechanisms for OIDC JWKS and Metadata Document as well as OIDC token cache. Specifically, inverted time comparisons cause the OIDC metadata and keys cache to never return cached values, resulting in unnecessary HTTP fetches, and the OIDC token cache to never invalidate, causing expired tokens to be reused. This issue is fixed in version 2. 1. 0.
AI Analysis
Technical Summary
The Data Sharing Framework (DSF) prior to version 2.1.0 contains a logic flaw in its OIDC JWKS and Metadata Document caches and OIDC token cache. The caches use an inverted time comparison (isBefore instead of isAfter), which causes the JWKS and metadata caches to always bypass cached values and fetch fresh data on every request. Conversely, the OIDC token cache never invalidates tokens due to the same inverted comparison, resulting in reuse of expired tokens. This vulnerability is classified under CWE-670 (Always-Incorrect Control Flow Implementation) and has a CVSS 4.0 base score of 6.3 (medium severity). The issue is resolved in DSF version 2.1.0.
Potential Impact
The vulnerability causes inefficient caching behavior for OIDC JWKS and metadata, leading to increased network requests and potential performance degradation. More critically, the OIDC token cache does not invalidate expired tokens, which could lead to authentication issues or token misuse depending on the token validation context. There are no known exploits in the wild. The impact is rated medium based on the CVSS score of 6.3.
Mitigation Recommendations
Upgrade the Data Sharing Framework to version 2.1.0 or later, where this caching logic flaw is fixed. No other mitigation or workaround is indicated. Patch status is not explicitly stated but the fix is included in version 2.1.0, so upgrading to this version or newer is the recommended remediation.
CVE-2026-40942: CWE-670: Always-Incorrect Control Flow Implementation in datasharingframework dsf
Description
CVE-2026-40942 affects the Data Sharing Framework (DSF) versions prior to 2. 1. 0. The vulnerability arises from incorrect time comparison logic in caching mechanisms for OIDC JWKS and Metadata Document as well as OIDC token cache. Specifically, inverted time comparisons cause the OIDC metadata and keys cache to never return cached values, resulting in unnecessary HTTP fetches, and the OIDC token cache to never invalidate, causing expired tokens to be reused. This issue is fixed in version 2. 1. 0.
CVSS v4.0
Score 6.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Data Sharing Framework (DSF) prior to version 2.1.0 contains a logic flaw in its OIDC JWKS and Metadata Document caches and OIDC token cache. The caches use an inverted time comparison (isBefore instead of isAfter), which causes the JWKS and metadata caches to always bypass cached values and fetch fresh data on every request. Conversely, the OIDC token cache never invalidates tokens due to the same inverted comparison, resulting in reuse of expired tokens. This vulnerability is classified under CWE-670 (Always-Incorrect Control Flow Implementation) and has a CVSS 4.0 base score of 6.3 (medium severity). The issue is resolved in DSF version 2.1.0.
Potential Impact
The vulnerability causes inefficient caching behavior for OIDC JWKS and metadata, leading to increased network requests and potential performance degradation. More critically, the OIDC token cache does not invalidate expired tokens, which could lead to authentication issues or token misuse depending on the token validation context. There are no known exploits in the wild. The impact is rated medium based on the CVSS score of 6.3.
Mitigation Recommendations
Upgrade the Data Sharing Framework to version 2.1.0 or later, where this caching logic flaw is fixed. No other mitigation or workaround is indicated. Patch status is not explicitly stated but the fix is included in version 2.1.0, so upgrading to this version or newer is the recommended remediation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-15T20:40:15.519Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e7e91619fe3cd2cdfaec51
Added to database: 4/21/2026, 9:16:06 PM
Last enriched: 4/29/2026, 11:12:13 AM
Last updated: 6/4/2026, 4:26:04 PM
Views: 64
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.