{"answers":{"affected":"1 open source package ship an affected version, including jose.","exploited":"There is no known exploitation of CVE-2026-65632 in the wild and no public exploit code.","fix":"Upgrade jose to 1.11.13 or later.","what":"CVE-2026-65632 is a medium-severity vulnerability in potatosalad jose, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-65632 and fix it if it is affected.\n\nWhat it is: CVE-2026-65632 is a medium-severity vulnerability in potatosalad jose, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-65632 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jose (Hex): affected from 1.0.0; fixed in 1.11.13\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-65632/ (Markdown: https://insights.sbomify.com/CVE-2026-65632/index.md)","id":"CVE-2026-65632","markdown":"https://insights.sbomify.com/CVE-2026-65632/index.md","name":"CVE-2026-65632","record":{"aliases":["AZL-111161","DEBIAN-CVE-2026-65632","EEF-CVE-2026-65632","GHSA-44hw-rpw9-mwg4","GHSA-6g34-xwc5-pgxj","UBUNTU-CVE-2026-65632"],"analysis":null,"analysis_generated_by":null,"assigner":"EEF","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"The jose library accepts ECDSA (ES256, ES256K, ES384, and ES512) JWS signatures of a non-canonical length. When verifying an ECDSA signature, jose_jwk_kty_ec:verify/4 in src/jwk/jose_jwk_kty_ec.erl splits the raw signature in half by its actual byte length (split_binary(Signature, byte_size(Signature) div 2)) instead of enforcing the fixed length required by RFC 7518 §3.4, and then decodes each half with crypto:bytes_to_integer/1, which ignores leading zero bytes.\n\nAs a result, an attacker who holds one valid token can prepend leading zero bytes to each of the R and S halves to produce longer signatures that still split evenly and decode to the same (r, s) pair, so many distinct signature byte strings all verify against the same key (signature malleability). This does not allow forging new payloads or impersonating a signer, because the underlying (r, s) values are unchanged. It does defeat any security control that assumes a valid token or its signature is unique, such as token-revocation-by-hash, replay or idempotency caches, and deduplication logic.\n\nThis issue affects jose: from 1.0.0 before 1.11.13.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ECDSA signature length is not validated in jose, allowing signature malleability","id":"CVE-2026-65632","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":5,"next":{"headline":"Purpose-limited JWT accepted as full bearer authentication in AshAuthentication","id":"CVE-2026-65633"},"packages":[{"ecosystem":"Hex","fixed":["1.11.13"],"introduced":["1.0.0"],"last_affected":[],"package":"jose","purl":"pkg:hex/jose","source":"EEF-CVE-2026-65632"}],"prev":{"headline":"Inefficient Algorithmic Complexity in erlang-jose allows an unauthenticated remote attacker to cause a CPU-exhaustion denial of service by s","id":"CVE-2026-65631"},"products":["jose"],"published":"2026-10-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"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-26","vendors":["potatosalad"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-65632/"}