p PatchFirst

CVE-2026-65631

CVE-2026-65631 · erlang-jose RSA JWK parsing attempts to factor an attacker-controlled modulus, enabling CPU-exhaustion denial of service

This page contains facts from public vulnerability sources. Check the original advisory before updating.

Inefficient Algorithmic Complexity in erlang-jose allows an unauthenticated remote attacker to cause a CPU-exhaustion denial of service by submitting a crafted RSA JSON Web Key. When an application parses an untrusted JWK through the public jose_jwk:from_binary/1 or jose_jwk:from_map/1 API (or the Elixir wrappers JOSE.JWK.from_binary/1 and JOSE.JWK.from_map/1), an RSA private key that supplies d, e, and n but omits all Chinese Remainder Theorem parameters (p, q, dp, dq, qi) is routed into convert_sfm_to_crt/1, which tries to recover the missing primes by factoring the modulus. The three integers are read straight from the base64url input and are never validated as a real RSA key. When the modulus cannot be split into two factors (for example, when it is itself prime), the search loop convert_sfm_to_crt_find_p/6 performs a modular exponentiation over the attacker-sized modulus on every iteration and never succeeds. A single request of a few hundred bytes forces close to one CPU-second of work before an internal one-second watchdog kills the worker, and a larger modulus raises the cost further. By flooding such requests an attacker can saturate every scheduler and deny service, without credentials, a valid RSA key, or any special configuration. This issue affects jose: from 1.7.7 before 1.11.13.

CVSS 6.9 · Medium · EPSS 0.2% · Fix available

Published
Updated

Stack: system

Affected products and versions

  • jose

    Versions
    • ≥ 1.7.7, < 1.11.13: Affected (semver)

    Update to 1.11.13

  • jose

    Versions
    • ≥ d19e1ba68d88c68d29aa942be2573a22dbafca1f, < bfd336c0062bff93e65d08c22361897e96afd956: Affected (git)

    No fix published

  • erlang-jose Debian:12

    Versions
    • 1.11.10-1
    • 1.11.10-1~bpo12+1
    • 1.11.12-1
    • 1.11.12-1.1
    • 1.11.12-2
    • 1.11.12-2~bpo13+1
    • 1.11.12-3
    • 1.11.12-3~bpo13+1
    • 1.11.5-1
    • 1.11.6-1
    • 1.11.6-1~bpo12+1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • erlang-jose Debian:13

    Versions
    • 1.11.10-1
    • 1.11.12-1
    • 1.11.12-1.1
    • 1.11.12-2
    • 1.11.12-2~bpo13+1
    • 1.11.12-3
    • 1.11.12-3~bpo13+1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • erlang-jose Debian:14

    Versions
    • 1.11.10-1
    • 1.11.12-1
    • 1.11.12-1.1
    • 1.11.12-2
    • 1.11.12-2~bpo13+1
    • 1.11.12-3
    • 1.11.12-3~bpo13+1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • jose Ubuntu:18.04:LTS

    Versions
    • 10-2
    • 10-2build1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • jose Ubuntu:20.04:LTS

    Versions
    • 10-2build2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • jose Ubuntu:22.04:LTS

    Versions
    • 10-3
    • 11-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • jose Ubuntu:24.04:LTS

    Versions
    • 11-2
    • 11-3
    • 11-3build1
    • 11-3build2
    • 13-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • jose Ubuntu:26.10

    Versions
    • 14-2build1
    • 14-2build2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • jose Ubuntu:26.04:LTS

    Versions
    • 14-2build1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →