Public vulnerability disclosure

CVE-2026-62374

SD JWT JS: Tampered disclosures silently dropped instead of rejected

publishedCWE-754CWE-176

SD JWT JS is a JavaScript implementation of the Selective Disclosure JWT (SD-JWT) specification. In version 0.19.0 and earlier, `@sd-jwt/decode`, also used by `@sd-jwt/core`, silently drops a tampered Disclosure whose digest no longer matches the Issuer-signed `_sd` array and returns a reduced claim set, reporting success while the Issuer signature remains valid. Both a tampered Disclosure that remains valid JSON and a Disclosure containing invalid UTF-8 bytes reach this silent-drop behavior. In the latter case, the `TextDecoder / Buffer` decoding path substitutes U+FFFD replacement characters, recovering syntactically valid disclosure data instead of rejecting the malformed input. This violates RFC 9901 section 7.1 step 5, which requires rejection of unreferenced Disclosures, and section 7.1 step 3 / section 4.2.1, which require rejection of invalid Disclosures. A malicious holder can exploit this omission primitive, including through `SDJwtInstance.verify()` when key binding is required. An on-path attacker can also tamper with a Disclosure when the relying party does not enforce key binding; enforced key binding rejects on-path tampering because it invalidates the KB-JWT `sd_hash` binding. If the relying party defaults to allowing access when a constraining age, role, or restriction claim is absent, the silent claim reduction can change an authorization decision without an error. This issue is fixed in `@sd-jwt/core` version 0.20.0; no patched version of the standalone `@sd-jwt/decode` package is identified.

Technical severity7.1 highCVSS 4.0 · CNA: GitHub_M
Published2026-10-29Source updated 2026-11-04
Collected2026-11-043 attributed sources

Fixes and workarounds

Fix

@sd-jwt/core (npm): OSV reports a fixed version 0.20.0. Check the advisory for supported release branches.

Source: OSV GHSA-f9j6-8p6x-r9j6

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
@sd-jwt/core
openwallet-foundation
<= 0.19.0 (affected) CNA: GitHub_M
@sd-jwt/decode
openwallet-foundation
<= 0.19.0 (affected) CNA: GitHub_M
@sd-jwt/decode

@sd-jwt/decode
npm
≥ 0; ≤ 0.19.0 (affected, semver); OSV events: introduced 0; last affected 0.19.0
Source events (semver)
[
  {
    "introduced": "0"
  },
  {
    "last_affected": "0.19.0"
  }
]

Other versions: unaffected
OSV GHSA-f9j6-8p6x-r9j6
@sd-jwt/core

@sd-jwt/core
npm
≥ 0; < 0.20.0 (affected, semver); OSV events: introduced 0; fixed 0.20.0
Source events (semver)
[
  {
    "introduced": "0"
  },
  {
    "fixed": "0.20.0"
  }
]

Other versions: unaffected
OSV GHSA-f9j6-8p6x-r9j6

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
4.0 / 7.1
high
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NCNA: GitHub_M

Exploit evidence

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide