SD JWT JS: Tampered disclosures silently dropped instead of rejected
Impact
SD JWT JS versions 0.19.0 and earlier silently drop tampered disclosures instead of rejecting them, potentially changing authorization decisions. This affects @sd-jwt/core and @sd-jwt/decode. A malicious holder or on-path attacker can exploit this weakness.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.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.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
openwallet-foundation · GitHub_M
@sd-jwt/core
1 range
openwallet-foundation · GitHub_M
@sd-jwt/core
Compare with this publisher’s ranges. This does not inspect your installation.
affected
<= 0.19.0
Other versions: unknown
openwallet-foundation · GitHub_M
@sd-jwt/decode
1 range
openwallet-foundation · GitHub_M
@sd-jwt/decode
Compare with this publisher’s ranges. This does not inspect your installation.
affected
<= 0.19.0
Other versions: unknown
Original source description
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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-62374View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.