Most recent entries from all

EUVD-2026-232630

2026-10-04T22:58:29.451018+00:00

EUVD-2026-232630

fkie_cve-2022-36083

2026-10-04T22:58:29.451061+00:00

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…

GHSA-jv3g-j58f-9mq9 — JOSE vulnerable to resource exhaustion via specifically crafted JWE

2026-10-04T22:58:29.451111+00:00

Affected: npm: jose, npm: jose-browser-runtime, npm: jose-node-cjs-runtime, npm: jose-node-esm-runtime

The PBKDF2-based JWE key management algorithms expect a JOSE Header Parameter named `p2c` ([PBES2 Count](https://www.rfc-editor.org/rfc/rfc7518.html#section-4.8.1.2)), 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.

### Impact

Under certain conditions (see below) it is possible to have the user's environment consume unreasonable amount of CPU time.

### Affected users

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 PBKDF2-based JWE Key Management Algorithm Identifiers are

- `PBES2-HS256+A128KW` - `PBES2-HS384+A192KW` - `PBES2-HS512+A256KW`

e.g.

```js const secret = new Uint8Array(16) const jwe = '...' // JWE from an untrusted party

await jose.compactDecrypt(jwe, secret) ```

You are NOT affected if any of t…

gsd-2022-36083

2026-10-04T22:58:29.451175+00:00

gsd-2022-36083

UBUNTU-CVE-2022-36083

2026-10-04T22:58:29.451189+00:00

Affected: Ubuntu:22.04:LTS: node-jose, Ubuntu:24.04:LTS: jose, Ubuntu:25.10: jose, Ubuntu:26.04:LTS: jose