Dsf Bpe Process Api V2
Approved changes feed: RSS · Atom
cpe:2.3:a:dev.dsf:dsf-bpe-process-api-v2:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Dev.Dsf (1b0ee4fd-442f-5204-9e2d-2bafc99c7054) |
|---|---|
| Product | Dsf Bpe Process Api V2 (b3aa1819-9b1a-564f-8179-949cbdc80a6a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-40942 |
vulnerable | 2026-06-08 08:03:14.474963 |
DSF: Inverted Time Comparison in OIDC JWKS and Token Cache
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, 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. This vulnerability is fixed in 2.1.0.
Published: 2026-04-21T21:09:44.537Z
Updated: 2026-04-22T18:11:33.794Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.