CVE-2025-27144

A flaw was found in GO-JOSE. In affected versions, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code uses 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. This issue could be exploied by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service.

A moderate-impact denial of service flaw was found in Go JOSE, the Go implementation of the JSON Object Signing and Encryption (JOSE) standards, which is shipped in a number of Red Hat offerings including Red Hat OpenShift and related container-based products. When parsing compact JWS or JWE input, Go JOSE used strings.Split(token, ".") to split tokens, which can consume excessive memory when processing maliciously crafted tokens containing a large number of "." characters. A remote attacker with no privileges or required user interaction could submit numerous malformed tokens to an application that passes attacker-controlled input to Go JOSE, causing memory exhaustion and a denial of service that affects only availability. Red Hat rates this issue as moderate impact, consistent with the upstream severity assessment. Fixes are being pursued by the affected product components; some components were determined not to be affected because the vulnerable code is not present or is not in an execute path.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

As a workaround, applications can pre-validate that payloads being passed to Go JOSE do not contain an excessive number of . characters.