Resource exhaustion in Go-Jose
CVE-2025-27144
- CVSS
- Not scored
- Public exploits
- None known
- EPSS
- 0.004 · 34.9th percentile
- Published
- 2025-02-24
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.
Published · last modified .
EPSS exploit prediction
EPSS 0.004, 34.9th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Go-Jose — versions >= 4.0.0, < 4.0.5
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 3 other repositories (carabiner-dev/lab-vexable-repo, fleaz/trivy-renderer, unikorn-cloud/releases). These reference the CVE in a list, notes or a scanner and are not exploit code for it.