CVE-2025-27144

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.

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.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Kodem intelligence

Version 4.0.5 fixes this issue

1. What is CVE-2025-27144? CVE-2025-27144 is a medium-severity uncontrolled resource consumption vulnerability in github.com/go-jose/go-jose/v4 (go), affecting versions < 4.0.5. It is fixed in 4.0.5, 3.0.4. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. Which packages are affected by CVE-2025-27144?
   • github.com/go-jose/go-jose/v4 (go) (versions < 4.0.5)
   • github.com/go-jose/go-jose/v3 (go) (versions < 3.0.4)
   • github.com/go-jose/go-jose (go) (versions < 3.0.4)
3. Is there a fix for CVE-2025-27144? Yes. CVE-2025-27144 is fixed in 4.0.5, 3.0.4. Upgrade to this version or later.
4. Is CVE-2025-27144 exploitable, and should I be worried? Whether CVE-2025-27144 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2025-27144 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2025-27144?
   • Upgrade github.com/go-jose/go-jose/v4 to 4.0.5 or later
   • Upgrade github.com/go-jose/go-jose/v3 to 3.0.4 or later
   • Upgrade github.com/go-jose/go-jose to 3.0.4 or later