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 Version 4.0.5 fixes this issue ### Workarounds Applications could pre-validate payloads passed to go-jose do not contain an excessive number of '.' characters. ### References This is the same sort of issue as in the golang.org/x/oauth2/jws package as CVE-2025-22868 and Go issue https://go.dev/issue/71490.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-27144US | — | — | ||
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)… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/go-jose/go-josePACKAGE
- https://github.com/go-jose/go-jose/commit/99b346cec4e86d102284642c5dcbe9bb0cacfc22WEB
- https://github.com/go-jose/go-jose/releases/tag/v4.0.5WEB
- https://github.com/go-jose/go-jose/security/advisories/GHSA-c6gw-w398-hv78WEB
- https://github.com/golang/go/issues/71490WEB
- https://go.dev/issue/71490WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-27144ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan