Github.Com Go-Jose Go-Jose V3 vulnerabilities

CVE-2026-34986 [HIGH] CWE-248 Go JOSE Panics in JWE decryption Go JOSE Panics in JWE decryption ### Impact Decrypting a JSON Web Encryption (JWE) object will panic if the `alg` field indicates a key wrapping algorithm ([one ending in `KW`](https://pkg.go.dev/github.com/go-jose/go-jose/v4#pkg-constants), with the exception of `A128GCMKW`, `A192GCMKW`, and `A256GCMKW`) and the `encrypted_key` field is empty. The panic happens when `cipher.KeyUnwrap()` in `key_wrap.go` attempts to allocate a slic

CVE-2025-27144 [HIGH] CWE-400 DoS in go-jose Parsing DoS in go-jose Parsing ### Impact When parsing compact JWS or JWE input, go-jose could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of '.' characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service. ### Patches Versio

CVE-2024-28180 [MEDIUM] CWE-409 Go JOSE vulnerable to Improper Handling of Highly Compressed Data (Data Amplification) Go JOSE vulnerable to Improper Handling of Highly Compressed Data (Data Amplification) ### Impact An attacker could send a JWE containing compressed data that used large amounts of memory and CPU when decompressed by Decrypt or DecryptMulti. Those functions now return an error if the decompressed data would exceed 250kB or 10x the compressed size (whichever is larger). Thanks t