Search threats, CVEs… ⌘K
← Back to CVE intelligence
CVE intelligence

CVE-2025-27144

Vulnerability intelligence

Published Feb 24, 2025Sources checked Oct 3, 2026
6.6MEDIUMCVSS out of 10
What this means

Review the available evidence

CVE-2025-27144 and is rated Medium severity with a CVSS score of 6.6. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Microsoft Security Response Center guidance

CBL-Mariner Releases

Vendor-listed releases
  • 1.14.4-4
  • 2.6.1-21
  • 0.37.0-2
  • 0.0.2-20
  • 1.12.15-2
  • 2.7.5-2
  • 1.57.0-13
  • 2.0.0-6
  • 1.11.2-19
  • 1.9.5-9
  • 1.31.0-8
  • 1.29.4-12
  • 1.55.0-23
  • 1.28.4-15
  • 1.14.2-10
  • 1.6.2-25
  • 1.7.7-11
  • 1.2.0-20
  • 2.4.0-27
  • 1.22.3-12
  • 1.6.26-10
  • 1.9.5-6
  • 2.14.1-3
  • 1.7.13-7
  • 2.62.0-7
  • 1.7.7-9
  • 1.30.10-3
  • 1.2.0-17
CISA KEVNot listedBased on the latest collected catalog
EPSS0.4%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2025-27144?

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.