NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
💧
💧 Hex
Not in CISA KEV
MEDIUM severity

erlang-jose vulnerable to denial of service via large p2c valueGHSA-9mg4-v392-8j68

MEDIUMFix: potatosalad/erlang-jose@718d213

GHSA-9mg4-v392-8j68 is a medium-severity (CVSS 5.3) Uncontrolled Resource Consumption vulnerability in jose. A fix is available for jose — see the affected versions and patch details below.

Also known asCVE-2023-50966
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9mg4-v392-8j68.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.00%0.46%0.92%1.39%0.0%0.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
💧jose

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Hex packages — download data is not available via public APIs for these ecosystems.

Description

erlang-jose (aka JOSE for Erlang and Elixir) through 1.11.6 allow attackers to cause a denial of service (CPU consumption) via a large p2c (aka PBES2 Count) value in a JOSE header.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
💧Hexjoseall versions1.11.7mix deps.update jose

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jose, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update jose to 1.11.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9mg4-v392-8j68 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

erlang-jose (aka JOSE for Erlang and Elixir) through 1.11.6 allow attackers to cause a denial of service (CPU consumption) via a large p2c (aka PBES2 Count) value in a JOSE header.
O3 Security · Impact-Aware SCA

Is GHSA-9mg4-v392-8j68 in your dependencies?

Find it across Hex, including transitive dependencies.

GHSA-9mg4-v392-8j68: jose DoS — Fixed in 1.11.7