github.com/go-jose/go-jose/v4
Affected
- introduced
0, fixed4.0.5(semver)
Fixed versions
4.0.5
Fix
- Fixed version
4.0.5go get github.com/go-jose/go-jose/[email protected]
Advisory
Also known as: CVE-2025-27144, GO-2025-3485
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.
Medium Basis: The source's own band: MODERATE
0, fixed 4.0.5 (semver)4.0.5
4.0.5go get github.com/go-jose/go-jose/[email protected]0, fixed 3.0.4 (semver)3.0.4
3.0.4go get github.com/go-jose/go-jose/[email protected]0, fixed 3.0.4 (semver)3.0.4
3.0.4go get github.com/go-jose/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0