JOSE is "JSON Web Almost Everything" - JWA, JWS, JWE, JWT, JWK, JWKS with no dependencies using runtime's native crypto in Node.js, Browser, Cloudflare Workers, Electron, and Deno. The PBKDF2-based JWE key management algorithms expect a JOSE Header Parameter named p2c PBES2 Count, which determines how many PBKDF2 iterations must be executed in order to derive a CEK wrapping key. The purpose of this parameter is to intentionally slow down the key derivation function in order to make password brute-force and dictionary attacks more expensive. This makes the PBES2 algorithms unsuitable for situations where the JWE is coming from an untrusted source: an adversary can intentionally pick an extremely high PBES2 Count value, that will initiate a CPU-bound computation that may take an unreasonable amount of time to finish. Under certain conditions, it is possible to have the user's environment consume unreasonable amount of CPU time. The impact is limited only to users utilizing the JWE decryption APIs with symmetric secrets to decrypt JWEs from untrusted parties who do not limit the accepted JWE Key Management Algorithms (alg Header Parameter) using the keyManagementAlgorithms (or algorithms in v1.x) decryption option or through other means. The v1.28.2, v2.0.6, v3.20.4, and v4.9.2 releases limit the maximum PBKDF2 iteration count to 10000 by default. It is possible to adjust this limit with a newly introduced maxPBES2Count decryption option. If users are unable to upgrade their required library version, they have two options depending on whether they expect to receive JWEs using any of the three PBKDF2-based JWE key management algorithms. They can use the keyManagementAlgorithms decryption option to disable accepting PBKDF2 altogether, or they can inspect the JOSE Header prior to using the decryption API and limit the PBKDF2 iteration count (p2c Header Parameter).
CVE-2022-36083
“—” beside the score: it is equal to NVD's CVSS score.
This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 1.5% (74th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMmedium confidence
- EG Risk
- 55EG Risk 55/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 1.5%
- EPSS %ILE
- 74th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 1.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 7, 2022
Last Modified
June 22, 2026
Advisory Details (3)
Auto-updated Jun 22, 2026Resource exhaustion via specifically crafted JWE · Advisory · panva/jose · GitHub
https://github.com/panva/jose/security/advisories/GHSA-jv3g-j58f-9mq9Release v4.9.2 (panva/jose)
Patch available: panva/jose v4.9.2
https://github.com/panva/jose/releases/tag/v4.9.2commit 03d6d013bf6e (panva/jose)
Patch available: panva/jose v5.8.0 (contains commit 03d6d013bf6e)
https://github.com/panva/jose/commit/03d6d013bf6e070e85adfe5731f526978e3e8e4dAffected Packages
(6 across 3 ecosystems)
npm(4)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| jose | — |
| — |
| jose-browser-runtime | — |
| — |
| jose-node-cjs-runtime | — |
| — |
| jose-node-esm-runtime | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| node-jose | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| node-jose | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 33× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 92 of 195 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 16:28 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-22 16:30 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-20 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-18 08:31 UTCEG score recompute
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-16 16:35 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-15 19:54 UTCOSV refresh
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-13 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-12 18:50 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-11 23:15 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-08 16:40 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-05 17:40 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
Show 67 moreShow fewer
- 2026-10-01 19:47 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-30 15:59 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-29 15:16 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-24 12:07 UTCOSV refresh
- 2026-09-22 14:45 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-19 15:38 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-17 19:24 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-15 03:07 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-11 14:50 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-07 15:58 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-05 04:48 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-27 14:22 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-20 22:52 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-18 15:28 UTCOSV refresh
- 2026-08-18 13:45 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-17 13:44 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-08-11 13:39 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-10 14:08 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-08 16:34 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-07 16:24 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-06 13:44 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-03 11:27 UTCOSV refresh
- 2026-08-02 02:24 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-01 04:13 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-07-30 16:25 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-07-28 15:33 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-07-26 14:52 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-07-25 14:15 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-07-24 14:15 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-07-23 14:16 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-07-23 02:12 UTCEG score recompute
- 2026-07-22 22:59 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-07-21 15:22 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
Related CVEs(same product + same CWE)
Same product
6 shownDebian:12:node-jose · npm:jose · npm:jose-browser-runtime
Frequently asked(5)
What is CVE-2022-36083?
When was the CVE record for CVE-2022-36083 published?
Is CVE-2022-36083 actively exploited?
What is the CVSS score of CVE-2022-36083?
How do I remediate CVE-2022-36083?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-36083
Is Your Infrastructure Affected by CVE-2022-36083?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.