CVE-2026-75522
Received Received - Intake

OpenID4VP Credential Chain Forgery via Subject DN Spoofing

Vulnerability report for CVE-2026-75522, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
openid4vp openid4vp 0.8.1
openeudi openid4vp to 0.8.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-347 The product does not verify, or incorrectly verifies, the cryptographic signature for data.
CWE-295 The product does not validate, or incorrectly validates, a certificate.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the OpenID4VP library versions prior to 0.8.1. It involves incorrect X.509 certificate chain validation where the system stops building the chain if a certificate's Subject Distinguished Name matches a trusted anchor's Subject DN, without verifying cryptographic closure. Attackers can exploit this by creating self-signed certificates that reuse a trusted anchor's Subject DN, tricking the system into accepting forged credentials as valid.

Detection Guidance

Detecting this vulnerability requires checking if your OpenID4VP library version is prior to 0.8.1. Use commands like 'npm list @openeudi/openid4vp' or 'grep "openid4vp" package.json' to verify the installed version. If the version is 0.8.0 or earlier, the system is vulnerable.

Impact Analysis

If you use OpenID4VP versions before 0.8.1, attackers could forge credentials that appear to be issued by trusted authorities. This could allow impersonation in systems relying on OpenID4VP for verification, such as eIDAS or EUDI deployments, potentially leading to unauthorized access or fraud.

Compliance Impact

This vulnerability could undermine compliance with GDPR and HIPAA by enabling impersonation of trusted issuers in credential verification systems. If exploited, attackers could forge credentials accepted as genuine, potentially violating data integrity and authenticity requirements under these regulations.

Mitigation Strategies

Immediately upgrade the OpenID4VP library to version 0.8.1 or later using 'npm update @openeudi/openid4vp'. Ensure the updated version enforces cryptographic closure checks instead of Subject DN equality for trust chain validation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-75522. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...