CVE-2026-65632

ECDSA signature length is not validated in jose, allowing signature malleability

  • Medium 5.1

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. As 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. This issue affects jose: from 1.0.0 before 1.11.13.

Key facts

Published
26 Oct 2026
Last changed
2 Nov 2026
Assigned by
EEF
EPSS
0.092% likely to be exploited in the next 30 days, higher than 0.523% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: poc; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.1CVSS 4.0, Mediumfrom the CNA (EEF)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

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

CAPEC-475 Signature Spoofing by Improper Validation (CNA impact statement)

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
potatosaladjose
  • Default status: unaffected
  • 1.0.0 up to but excluding 1.11.13 (affected)
potatosaladjose
  • Default status: unaffected
  • a7746ecd4950f85a393136e449a91dac62b5c429 up to but excluding 72ce1866622b9329347dc52a94173ac0317bc9cf (affected)

Timeline

  1. 26 Oct 2026 Published

Weakness

References