cve.bz

CVE-2026-62374 openwallet-foundation: Improper Handling of Unicode Encoding

7.1 highEPSS 0.2%Fix available

High (7.1) in openwallet-foundation. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in @sd-jwt/core 0.20.0.

On this page
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.

Severity

CVSS 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:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-11-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-176 Improper Handling of Unicode Encoding
CWE-754 Improper Check for Unusual or Exceptional Conditions
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @sd-jwt/core (npm): fixed in 0.20.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-62374 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-62374?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-62374?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-62374 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
openwallet-foundation @sd-jwt/core<= 0.19.0
openwallet-foundation @sd-jwt/decode<= 0.19.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-f9j6-8p6x-r9j6npm@sd-jwt/decode<=0.19.0no fix published
GHSA-f9j6-8p6x-r9j6npm@sd-jwt/core<0.20.00.20.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because exploiting the issue requires an attacker to possess valid token presentation capabilities and relies on verifiers using negative authorization models where the absence of a constraint grants privilege. In standard production environments, relying applications generally enforce explicit positive assertion of required claims, mitigating unauthorized elevation. Furthermore, the affected JavaScript library is not included or deployed in core Red Hat enterprise distributions.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-62374.

Attack patterns (CAPEC)

  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON