{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-62374 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-62374 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-62374 is a high-severity vulnerability in openwallet-foundation @sd-jwt/core, published on 29 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-62374 and fix it if it is affected.\n\nWhat it is: CVE-2026-62374 is a high-severity vulnerability in openwallet-foundation @sd-jwt/core, published on 29 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-62374 in the wild and no public exploit code.\n\nAffected product: openwallet-foundation @sd-jwt/core. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-62374/ (Markdown: https://insights.sbomify.com/CVE-2026-62374/index.md)","id":"CVE-2026-62374","markdown":"https://insights.sbomify.com/CVE-2026-62374/index.md","name":"CVE-2026-62374","record":{"aliases":["GHSA-f9j6-8p6x-r9j6"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"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","version":"4.0"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"},{"id":"CWE-176","name":"Improper Handling of Unicode Encoding"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SD JWT JS: Tampered disclosures silently dropped instead of rejected","id":"CVE-2026-62374","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Vikunja: Plaintext storage of password-reset/email-confirm tokens in database enables account takeover on DB read access","id":"CVE-2026-62376"},"packages":[],"prev":{"headline":"KubeEdge: Command Injection in NodeUpgradeJob - RCE on edge nodes via v1alpha2 API","id":"CVE-2026-62371"},"products":["@sd-jwt/core","@sd-jwt/decode"],"published":"2026-10-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-29","vendors":["openwallet-foundation"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-62374/"}