cve.bz

CVE-2026-65632 potatosalad jose

5.1 mediumEPSS 0.09%Fix available

Medium (5.1) in potatosalad jose. EPSS 0.09% estimated probability of exploitation activity in the next 30 days. Fixed in jose 1.11.13.

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

Severity

CVSS 4.0

5.1 medium
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
EPSS
0.09% (unchanged from 0.09% a week ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-65632 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-65632?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-65632?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-65632 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
potatosalad josefrom 1.0.0 before 1.11.13

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-65632Hexjose>=1.0.0 <1.11.131.11.13
EEF-CVE-2026-656321.11.12, 1.11.11, 1.11.10, 1.11.9, 1.11.8 and 40 moreno fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13erlang-joseno fix listedDEBIAN-CVE-2026-65632
Debian14erlang-jose1.11.13-1DEBIAN-CVE-2026-65632
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 3 morejoseno fix listedUBUNTU-CVE-2026-65632
Azure Linux3joseno fix listedAZL-111161
Azure Linux3rabbitmq-serverno fix listedAZL-112193

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as a Moderate impact because it allows an attacker possessing a valid signature to bypass uniqueness checks such as deduplication or replay caches, but cannot be leveraged to forge signatures, alter token claims, or achieve unauthorized privilege elevation. Within Red Hat environments, exposure is restricted to applications using Erlang-based Jose services where token identity is tracked via raw cryptographic hashes rather than verified internal identifiers. Because creating modified signatures requires an attacker to already possess an authorized token, arbitrary data cannot be signed and confidentiality is unaffected.

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-65632.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

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

References

Check your stackJSON