What is CVE-2026-40942?

CVE-2026-40942 is a medium-severity security vulnerability in dev.dsf:dsf-bpe-process-api-v2 (maven), affecting versions < 2.1.0. No fixed version is listed yet.

Which packages are affected by CVE-2026-40942?

dev.dsf:dsf-bpe-process-api-v2 (maven) versions < 2.1.0; dev.dsf:dsf-bpe-server (maven) versions < 2.1.0.

Is there a fix for CVE-2026-40942?

No fixed version is listed for CVE-2026-40942 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2026-40942 exploitable, and should I be worried?

Whether CVE-2026-40942 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-40942 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-40942 in dev.dsf:dsf-bpe-process-api-v2

Q: Which packages are affected by CVE-2026-40942?

dev.dsf:dsf-bpe-process-api-v2 (maven) versions < 2.1.0; dev.dsf:dsf-bpe-server (maven) versions < 2.1.0.

Q: Is there a fix for CVE-2026-40942?

No fixed version is listed for CVE-2026-40942 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is CVE-2026-40942 exploitable, and should I be worried?

Whether CVE-2026-40942 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-40942 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Summary

Data Sharing Framework has an Inverted Time Comparison in OIDC JWKS and Token Cache

Affected Components

DSF FHIR Server with enabled bearer-token authentication or back-channel logout.
DSF BPE Server with enabled bearer-token authentication or back-channel logout.
DSF BPE Server API v2 process plugins using FHIR client connections with configured OIDC authentication.
The OIDC JWKS and Metadata Document caches used an inverted time comparison (isBefore instead of isAfter), causing the cache to never return cached values. Every incoming request triggered a fresh HTTP fetch of the OIDC Metadata Document and JWKS keys from the OIDC provider.
The OIDC token cache for the FHIR client connections used an inverted time comparison (isBefore instead of isAfter), causing the cache to never invalidate. Every incoming request returned the same OIDC token even if expired.

Fix (commits 31c2e974d, d3ca59b4d)

Fixed cache timeout comparison from isBefore to isAfter in BaseOidcClientWithCache (configuration and JWKS caches) and OidcClientWithCache (configuration, JWKS, and access token caches)
Added configurable cache timeouts via dev.dsf.server.auth.oidc.provider.client.cache.timeout.configuration.resource and dev.dsf.server.auth.oidc.provider.client.cache.timeout.jwks.resource (default: PT1H)

Impact

Performance: Every OIDC-authenticated request added network round-trips to the OIDC provider, increasing latency
Reliability: Cached OIDC tokens become unusable after expiration and can only be invalidated by restart of the BPE.
If the OIDC provider is temporarily unreachable, all requests fail immediately instead of using cached keys
Load: Unnecessary load on the OIDC provider, potentially causing rate limiting

Affected versions

dev.dsf:dsf-bpe-process-api-v2 (< 2.1.0) dev.dsf:dsf-bpe-server (< 2.1.0)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

No fixed version is listed for CVE-2026-40942 yet.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-40942? CVE-2026-40942 is a medium-severity security vulnerability in dev.dsf:dsf-bpe-process-api-v2 (maven), affecting versions < 2.1.0. No fixed version is listed yet.
Which packages are affected by CVE-2026-40942?
- dev.dsf:dsf-bpe-process-api-v2 (maven) (versions < 2.1.0)
- dev.dsf:dsf-bpe-server (maven) (versions < 2.1.0)
Is there a fix for CVE-2026-40942? No fixed version is listed for CVE-2026-40942 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2026-40942 exploitable, and should I be worried? Whether CVE-2026-40942 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-40942 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.