CVE-2025-27144
Description
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to version 4.0.5, 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. Version 4.0.5 fixes this issue. As a workaround, applications could pre-validate that payloads passed to Go JOSE do not contain an excessive number of `.` characters.
How to fix
- github.com/go-jose/go-jose/v44.0.5 or later
- github.com/go-jose/go-jose/v33.0.4 or later
- github.com/go-jose/go-jose3.0.4 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| github.com/go-jose/go-jose/v4Go | v < 4.0.5 | 4.0.5 |
| github.com/go-jose/go-jose/v3Go | v < 3.0.4 | 3.0.4 |
| github.com/go-jose/go-joseGo | v < 3.0.4, No range specified | 3.0.4 |
| github.com/square/go-joseGo | No range specified | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.