CVE-2026-65632: potatosalad jose · Improper Verification of Cryptographic Signature
Affects potatosalad joseSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 1.11.13 when convenient.
Data as of 26 Oct 2026, 20:14 UTC
- Patch
- Available – fixed in 1.11.13, 72ce1866622b9329347dc52a94173ac0317bc9cf
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade jose to 1.11.13; jose to 72ce1866622b9329347dc52a94173ac0317bc9cf.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| potatosaladjose | Affected
| Fixed in
|
| josepotatosalad/erlang-jose | Affected
| Fixed in
|
Hexjosepkg:hex/joseOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:potatosalad:jose:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in jose version 1.11.13 that fixes this improper signature verification. Users should upgrade to version 1.11.13 or later to remediate this issue. Since a fix exists, applying the official update is the recommended mitigation.
Description
The jose library versions from 1.0.0 up to but not including 1.11.13 improperly verify ECDSA JWS signatures by accepting signatures of non-canonical length. This signature malleability allows multiple distinct signature byte strings to verify as valid for the same token, defeating security controls that rely on signature uniqueness such as token revocation by hash, replay caches, and deduplication. The underlying cryptographic signature values (r, s) remain unchanged, so forging new payloads or impersonating signers is not possible. A fix is available in version 1.11.13.
References
- github.com/potatosalad/erlang-jose/security/advisories/GHSA-44hw-rpw9-mwg4 (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-65632.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-65632 (opens in a new tab)
- github.com/potatosalad/erlang-jose/commit/a7746ecd4950f85a393136e449a91dac62b5c429 (opens in a new tab)
- github.com/potatosalad/erlang-jose/commit/72ce1866622b9329347dc52a94173ac0317bc9cf (opens in a new tab)