Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/go-jose/go-jose/commit/99b346cec4e86d102284642c5dcbe9bb0cacfc
- https://github.com/go-jose/go-jose/releases/tag/v4.0.5
- https://github.com/go-jose/go-jose/security/advisories/GHSA-c6gw-w398-hv78
FAQ
What is CVE-2025-27144?
CVE-2025-27144 is a documented vulnerability. 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...
How severe is CVE-2025-27144?
CVSS scoring is not yet available for CVE-2025-27144. Check NVD for updates.
Is there a patch for CVE-2025-27144?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.