Vulnerability · CVE-2026-65628
jose_jwk:shared_secret/2 (exposed in Elixir as JOSE.JWK.shared_secret/2) derives an ECDH shared secret from two JWKs.
Published Oct 26, 2026 · catalog updated Oct 27, 2026 · jose_jwk:shared_secret/2 (exposed in Elixir
Last checked Nov 5, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-65628. EPSS is 0.14%. Act only if a listed version of jose_jwk:shared_secret/2 (exposed in Elixir is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (jose_jwk:shared_secret/2 (exposed in Elixir).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.14%
- Remediation
- Advisory link
- Affected products
- Debian:12 erlang-jose · Debian:13 erlang-jose · Debian:14 erlang-jose · Hex jose
## Summary (exposed in Elixir as ) derives an ECDH shared secret from two JWKs. Its first function clause only matches when both JWKs carry the same key type ( ) module, and its fallback clause re-invokes itself as . Because returns an already-parsed record unchanged, passing two JWKs whose key types differ (for example an EC key and an RSA key) makes the fallback clause re-enter with identical arguments, producing an unbounded tail-recursive loop that never returns and never crashes. An application that derives a shared secret from an externally supplied peer public key without first checking that the peer key's type and curve match its own key can be driven into this loop by an attacker-controlled JWK, pinning an Erlang scheduler at 100% CPU. Repeated requests exhaust the available schedulers, resulting in a denial of service. This issue affects jose: from 1.5.0 before 1.11.13. ## Workarounds Before calling , verify that the externally supplied peer key's type ( ) and curve match your own key, and reject any key whose type does not match before attempting derivation.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Debian:12 erlang-jose1.11.10-1, 1.11.10-1~bpo12+1, 1.11.12-1
- Debian:13 erlang-jose1.11.10-1, 1.11.12-1, 1.11.12-1.1
- Debian:14 erlang-jose1.11.10-1, 1.11.12-1, 1.11.12-1.1
- Hex jose1.5.0 → 1.11.13
How to fix CVE-2026-65628
Upgrade
CVE-2026-65628 lists a fix boundary at 1.11.13. Compare the installed build with that boundary before you change production.
Version check
Seen in 1.11.10-1 · 9 other packages on the advisory
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-65628. EPSS is 0.14%. Act only if a listed version of jose_jwk:shared_secret/2 (exposed in Elixir is installed.
Which versions are affected?
Compare what you have installed with 1.11.10-1, 1.11.10-1~bpo12+1, 1.11.12-1, 1.11.10-1, 1.11.12-1, 1.11.12-1.1, 1.5.0 → 1.11.13. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-674. EPSS 0.14%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 26, 2026 · GitHub Advisory Database
Fix available
jose fixed in 1.11.13
Oct 26, 2026 · Trivy Vulnerability DB
Detected
jose_jwk:shared_secret/2 (exposed in Elixir as JOSE.JWK.shared_secret/2) derives an ECDH shared secret from two JWKs. Its first function clause only matches when both JWKs carry the same key type (kty) module, and its fallback clause re-invokes itself as shared_secret(from(YourJWK), from(MyJWK)). Because from/1 returns an already-parsed jose_jwk record unchanged, passing two JWKs whose key types d
Oct 27, 2026 · GitHub Advisory Database
Fix available
jose fixed in 1.11.13
Oct 27, 2026 · Trivy Vulnerability DB
Updated
jose_jwk:shared_secret/2 (exposed in Elixir as JOSE.JWK.shared_secret/2) derives an ECDH shared secret from two JWKs. Its first function clause only matches when both JWKs carry the same key type (kty) module, and its fallback clause re-invokes itself as shared_secret(from(YourJWK), from(MyJWK)). Because from/1 returns an already-parsed jose_jwk record unchanged, passing two JWKs whose key types d
Sources
- CVE.orgVulnerability recordCVE-2026-65628
Official CVE identifier
cve.org - GitHub Advisory DatabasePackage advisoryGHSA-fpj2-9h59-32pp
GitHub Advisory Database record mirrored by OSV.
github.com - OpenSSF OSV / OSV ScannerPackage advisoryEEF-CVE-2026-65628
Infinite recursion (CPU denial-of-service) in JOSE.JWK.shared_secret/2 on mismatched key types
osv.dev - Trivy Vulnerability DBPackage advisoryDEBIAN-CVE-2026-65628
jose_jwk:shared_secret/2 (exposed in Elixir as JOSE.JWK.shared_secret/2) derives an ECDH shared secret from two JWKs. Its first function clause only matches when both JWKs carry the same key type (kty) module, and its fallback clause re-invokes itself as shared_secret(from(YourJW
osv.dev
References
Freshness
Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- GitHub Advisory DatabaseNov 1, 2026
- OpenSSF OSV / OSV ScannerNov 1, 2026
- CVE.orgOct 27, 2026
- Trivy Vulnerability DBOct 27, 2026