cve.bz

CVE-2026-65630 potatosalad jose: Observable Timing Discrepancy

5.9 mediumEPSS 0.1%Fix available

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

On this page
Observable Timing Discrepancy vulnerability in potatosalad jose allows recovery of a long-term X25519 private key through a timing side channel in the pure-Erlang Curve25519 fallback. The pure-Erlang X25519 implementation performs scalar multiplication over the secret private key using a recursive Montgomery ladder (jose_jwa_x25519:curve25519/2) whose clauses branch on individual bits of the clamped private scalar, and whose per-step operations (jose_jwa_x25519:montgomery_add/3 and jose_jwa_x25519:montgomery_double/1) and field inversion are built from value-dependent Erlang bignum arithmetic (multiplication, remainder, and modular exponentiation). Although the ladder is operation-count balanced and fixed at 254 steps, the concrete integer values processed at each step, and therefore the running time, depend on the secret scalar. The execution time of the public entry points jose_jwa_x25519:scalarmult/2, jose_jwa_x25519:x25519/2, jose_jwa_x25519:x25519_base/1, and jose_jwa_x25519:sk_to_pk/1 is thus a function of the private key. This path is reachable from the public API, most notably when a service decrypts attacker-supplied ECDH-ES (JWE) messages with a long-term X25519 key (for example through JOSE.JWK.box_decrypt_ecdh_es/2, which reaches jose_jwa_curve25519:x25519_shared_secret/2 and the ladder). An attacker who can submit ciphertexts and measure decryption timing can, in principle, recover the private key bit by bit, defeating the resistance X25519 was designed to provide. Recovery of the key compromises the confidentiality and authenticity of all data protected by it. This issue affects jose: from 1.10.0 before 1.11.13.

Severity

CVSS 4.0

5.9 medium
CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-208 Observable Timing Discrepancy
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-65630 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-65630?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-65630?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-65630 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.10.0 before 1.11.13

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-65630Hexjose>=1.10.0 <1.11.131.11.13
EEF-CVE-2026-656301.11.12, 1.11.11, 1.11.10, 1.11.9, 1.11.8 and 8 moreno fix published

Linux distributions

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

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

Red Hat has evaluated this vulnerability as having a Moderate severity because successful exploitation demands high attack complexity, requiring precise timing analysis across numerous decryption operations under conditions where network jitter is minimized. The vulnerability is confined to the pure-Erlang software fallback routines, which are only invoked when native cryptographic acceleration via OpenSSL is unavailable. Standard enterprise environments generally rely on native crypto NIFs, significantly limiting real-world exposure.

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

Attack patterns (CAPEC)

  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-541 Application Fingerprinting Severity: Low
  • CAPEC-580 System Footprinting Likelihood: Low · Severity: Low

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

References

Check your stackJSON