Skip to main content
Menu
CVEs

Eclipse Dataspace Components credential verification bypass in DCP presentations

Affects Eclipse Dataspace Components connector 0.11.0 to 0.18.1 and 1.0.0-RC1 to 1.0.0-RC6 in its decentralized-claims, jwt-verifiable-credentials and ldp-verifiable-credentials modules. No fixed version is listed.

CVE-2026-126086Published November 19, 2026, updated

8.8HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Eclipse Dataspace Components (EDC) Connector has a credential verification bypass in how it handles Decentralized Claims Protocol (DCP) presentations. Remotely, without logging in, an attacker can present credentials that appear to be issued by any trusted issuer, even though they do not hold them.

Written by a model

Original description

In Eclipse Dataspace Components (EDC) – Connector (org.eclipse.edc:decentralized-claims-*, org.eclipse.edc:jwt-verifiable-credentials, org.eclipse.edc:ldp-verifiable-credentials) there's a credential verification bypass in Decentralized Claims Protocol (DCP) presentation handling: a participant can present credentials appearing to be issued by any trusted issuer without holding them.

Who should check

Teams running Eclipse EDC connectors 0.11.0 to 0.18.1 or 1.0.0-RC1 to 1.0.0-RC6 that use DCP credential presentation via the decentralized-claims, jwt-verifiable-credentials or ldp-verifiable-credentials modules.

“`>= 0.11.0, <= 0.18.1`, `1.0.0-RC1` to `1.0.0-RC6`”

gitlab.eclipse.org

What to do

Workaround: The checked facts do not name a workaround. Limiting use of the affected DCP presentation handling is not described in the sources checked.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126086 (In Eclipse Dataspace Components (EDC) – Connector (`org.eclipse.edc:decentralized-claims-*`, `org.eclipse.edc:jwt-verifiable-credentials`…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126086 (entry last updated 2026-11-19):
Affected:
- Eclipse Foundation Eclipse Dataspace Components: from 0.11.0, through 0.18.1; from 1.0.0-RC1, through 1.0.0-RC6
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affected EDC Connector versions 0.11.0 to 0.18.1 and 1.0.0-RC1 to 1.0.0-RC6 (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/566)
- Affected modules are the decentralized-claims, jwt-verifiable-credentials and ldp-verifiable-credentials packages of EDC (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/566)
- The flaw is in Decentralized Claims Protocol (DCP) presentation handling (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/566)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126086 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126086 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/566
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126086
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126086"}.

Affected versions

cve.now Index

34Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 8.8
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 79 if added to CISA KEV
  • Would score about 74 if CISA's SSVC rates exploitation active
  • Would score about 39 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkgitlab.eclipse.org · security/cve-assignment/-/work_items/566
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-126086
RecordNVD · CVE-2026-126086

Questions about CVE-2026-126086

Is CVE-2026-126086 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A participant can present credentials that appear to be issued by any trusted issuer without actually holding them. This bypasses credential verification in Decentralized Claims Protocol (DCP) presentation handling.

Source: gitlab.eclipse.org

Which versions are affected by CVE-2026-126086?

Eclipse Dataspace Components: from 0.11.0 through 0.18.1; from 1.0.0-RC1 through 1.0.0-RC6.

Source: cve.now feed data

Am I affected, and how do I check?

The listed ranges are EDC Connector 0.11.0 to 0.18.1 and 1.0.0-RC1 to 1.0.0-RC6, in the decentralized-claims-*, jwt-verifiable-credentials and ldp-verifiable-credentials packages. To check a deployment, compare the EDC connector version in use with these ranges and look at whether those packages are in its dependencies.

Source: gitlab.eclipse.org

How do I fix CVE-2026-126086?

The checked facts do not name a fixed version or patch identifiers, so no upgrade target can be given from them. Check the advisory for an update that names a fixed release.

Source: gitlab.eclipse.org

What if there's no patch?

The checked facts do not name a workaround. Limiting use of the affected DCP presentation handling is not described in the sources checked.

Source: gitlab.eclipse.org

No corrections so far. Something wrong on this page? Report an error.