Skip to main content
Menu
CVEs

CVE

OpenID4VP forged credential acceptance in X.509 chain validation

Only affects @openeudi/openid4vp 0.8.0 and earlier when a relying party verifies mdoc or SD-JWT VC presentations via TrustEvaluator or the credential-parsing API. Fixed in 0.8.1.

CVE-2026-75522Published Updated Summary written by a model

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.8.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.8.1.

Summary

OpenID4VP, an open-source credential parsing library for SD-JWT VC and mDOC/mDL formats, can be attacked remotely without logging in. An attacker can submit a self-signed certificate that reuses a trusted authority's subject name, which gets credentials signed with the attacker's own key accepted as issued by that trusted authority.

Original description

OpenID4VP is an open-source credential parsing library for SD-JWT VC and mDOC/mDL formats. Prior to 0.8.1, src/trust/ChainBuilder.ts ChainBuilder.tryBuild() terminates chain construction when an attacker-controlled certificate Subject Distinguished Name equals a trusted anchor subject, without verifying cryptographic closure to the anchor public key. A remote unauthenticated attacker can supply a self-signed leaf or intermediate that reuses the trusted Subject Distinguished Name and have credentials signed by the attacker key accepted as issued by the trusted authority. The public src/trust/TrustEvaluator.ts TrustEvaluator.evaluate() path compounds the error by matching a terminus through serialNumber and falling back to anchors[0], which can attribute the forged chain to genuine trusted-authority metadata. This issue is fixed in version 0.8.1.

Who should check

Teams running @openeudi/openid4vp 0.8.0 or earlier to verify OpenID4VP mdoc or SD-JWT VC presentations, such as eIDAS / EUDI age or identity verification deployments

“Affected versions <= 0.8.0”

github.com

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 0.8.1.

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-75522 (OpenID4VP: X.509 chain validation accepts a forged certificate that reuses a trusted anchor's Subject DN without verifying its signature), 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-75522 (entry last updated 2026-11-18):
Affected:
- openeudi openid4vp: fixed in 0.8.1
Fixed versions: 0.8.1.
Conditions (all must be true for the bug to be hit):
- Affected package @openeudi/openid4vp version 0.8.0 or earlier (fixed in 0.8.1) (source: https://github.com/openeudi/openid4vp/security/advisories/GHSA-4c2f-96cf-f5fc)
- Relying party uses the library to verify OpenID4VP presentations (mdoc / SD-JWT VC) via TrustEvaluator or the credential-parsing API (source: https://github.com/openeudi/openid4vp/security/advisories/GHSA-4c2f-96cf-f5fc)
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-75522 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-75522 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://github.com/openeudi/openid4vp/security/advisories/GHSA-4c2f-96cf-f5fc
- https://github.com/openeudi/openid4vp/pull/25
- https://github.com/openeudi/openid4vp/commit/a3ffd435aadd61aff1f75ec4b2e1a0f44ffabf16
- https://github.com/openeudi/openid4vp/releases/tag/v0.8.1
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-75522
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-75522"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • openeudi openid4vp

    fixed in 0.8.1

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · openeudi/openid4vp · Advisory GHSA-4c2f-96cf-f5fc
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-75522
RecordNVD · CVE-2026-75522
Other links 3
RepositoryGitHub · openeudi/openid4vp · Pull request #25
RepositoryGitHub · openeudi/openid4vp · Commit a3ffd435
RepositoryGitHub · openeudi/openid4vp · Release v0.8.1

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-75522

Is CVE-2026-75522 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?

The library's X.509 chain validation can accept a forged certificate that reuses a trusted anchor's Subject DN without checking its signature. A forged credential signed with the attacker's own key can then be accepted as issued by a trusted authority, impersonating that issuer.Source: github.com

Which versions are affected by CVE-2026-75522?

openid4vp: before 0.8.1.Source: cve.now feed data

Am I affected, and how do I check?

Versions 0.8.0 and earlier of @openeudi/openid4vp are affected, but only where a relying party uses the library to verify OpenID4VP presentations (mdoc or SD-JWT VC) through TrustEvaluator or the credential-parsing API. To check, look at the installed version of @openeudi/openid4vp in your package manifest or lockfile and see whether those APIs are used.Source: github.com

How do I fix CVE-2026-75522?

Upgrade @openeudi/openid4vp to version 0.8.1, which contains the fix.Source: github.com

More CVEs