CVE-2026-65628 potatosalad CVE debrief

Who should care

Elixir developers and administrators using the jose package should assess exposure and verify versions. Defenders should prioritize verifying and updating jose package versions to prevent potential denial-of-service attacks. This includes reviewing application code for JOSE.JWK.shared_secret/2 usage and implementing input validation for externally supplied peer public keys.

Why it matters

CVE-2026-65628 is a denial-of-service vulnerability in the jose package for Elixir. Defenders should prioritize verifying and updating jose package versions to prevent potential denial-of-service attacks. Elixir developers and administrators using the jose package should assess exposure and verify versions.

• Denial of service through scheduler exhaustion
• Potential for CPU pinning at 100%
• Exhaustion of available schedulers

Technical summary

The jose_jwk:shared_secret/2 function in Elixir can enter an unbounded loop when supplied with JWKs of different key types, leading to scheduler exhaustion and denial of service. This issue affects jose versions from 1.5.0 before 1.11.13. 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.

Defensive priority

Defenders should prioritize verifying and updating jose package versions to prevent potential denial-of-service attacks.

Recommended defensive actions

• Verify jose package version and update to 1.11.13 or later
• Review application code for JOSE.JWK.shared_secret/2 usage
• Implement input validation for externally supplied peer public keys
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. However, the corpus does not establish versions, exploitation, impact, or remediation beyond vendor-provided information. Defenders should verify jose package versions and review application code for JOSE.JWK.shared_secret/2 usage. The vulnerability can cause scheduler exhaustion and denial of service.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.