# CVE-2025-27144: Go JOSE's Parsing Vulnerable to Denial of Service > An attacker can cause memory exhaustion and denial of service by sending maliciously crafted JWT tokens with excessive delimiters to applications using the Go JOSE library. - **Severity:** Medium 6.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Feb 2025 - **Updated:** 25 Feb 2025 - **Also known as:** ALSA-2025:19566, ALSA-2025:7389, ALSA-2025:7397, ALSA-2025:7459, ALSA-2025:7467, AZL-57096, AZL-57099, AZL-57102, AZL-57105, AZL-57108, AZL-57111, AZL-57114, AZL-57117, AZL-57120, AZL-57123, AZL-57126, AZL-57129, AZL-57132, AZL-57135, AZL-57138, AZL-57144, AZL-57147, AZL-57153, AZL-57162, AZL-57165, AZL-57168, AZL-57171, AZL-57174, AZL-57177, AZL-57180, AZL-57183, AZL-57186, AZL-57192, AZL-57195, AZL-57198, AZL-57201, AZL-57204, AZL-57207, CLEANSTART-2026-EM35867, CLEANSTART-2026-WB96914, CLSA-2025-1752088672, CLSA-2025-1764152728, CLSA-2025-1766596893, CLSA-2026-1791280549, DEBIAN-CVE-2025-27144, GHSA-c6gw-w398-hv78, GO-2025-3485, MINI-26c5-x6cc-96cr, MINI-354x-mgr3-8wgj, MINI-386p-7h86-69j3, MINI-3hpv-hg4h-xhcm, MINI-434j-cwcr-j6fj, MINI-4cjg-fx72-fh6j, MINI-56qp-4hrm-g2cg, MINI-5875-j95q-vcjg, MINI-5c26-v7h4-6649, MINI-5p57-3xjx-7q3q, MINI-5r4p-j7cm-756g, MINI-6hjq-rxv2-8pvj, MINI-6x99-gpr8-7q55, MINI-96j5-m6vp-q457, MINI-98f4-8fh4-xx5q, MINI-c2r8-8347-5c8j, MINI-cch2-7gp7-pqj7, MINI-cw65-mxmp-c5hp, MINI-f89w-qf6g-mv52, MINI-fg3j-j78x-3grr, MINI-fjph-7vr4-rgx6, MINI-g2m8-q9rc-2r74, MINI-hjp8-w4pp-3qhr, MINI-mfc3-66w7-jf8v, MINI-mh9m-6r7r-45jj, MINI-mjmf-3gx2-35w5, MINI-p77v-j94p-hxx6, MINI-p95r-24gv-vr57, MINI-pcwh-p4cq-cgvr, MINI-pxfv-v4hx-vjqj, MINI-qm94-xv9v-mjv5, MINI-qpmf-f5wc-f7fx, MINI-qr9w-w3j5-648x, MINI-qvf6-6r95-v5cg, MINI-rfh7-9mr8-phxf, MINI-rvhc-r8p7-h9fv, MINI-vrh9-j9c8-x7hm, MINI-w4wm-6w2x-qf9w, MINI-w77v-w77j-v6q4, MINI-w9h4-hvm6-xww9, MINI-wjpm-j337-hxpq, MINI-x9cq-mc23-vqqw, MINI-xc7f-vrxx-344q, MINI-xvj6-qf8r-mvm5, OESA-2025-2176, OESA-2025-2177, RHSA-2025:19566, RHSA-2025:19594, RHSA-2025:3061, RHSA-2025:3068, RHSA-2025:7389, RHSA-2025:7397, RHSA-2025:7459, RHSA-2025:7467, RLSA-2025:7389, RLSA-2025:7397, RLSA-2025:7459, RLSA-2025:7467, SUSE-SU-2025:0772-1, SUSE-SU-2025:0785-1, SUSE-SU-2025:0786-1, SUSE-SU-2025:0811-1, SUSE-SU-2025:0812-1, SUSE-SU-2025:1009-1, SUSE-SU-2025:1010-1, SUSE-SU-2025:1011-1, UBUNTU-CVE-2025-27144, openSUSE-SU-2025:0080-1, openSUSE-SU-2025:14865-1, openSUSE-SU-2025:14871-1, openSUSE-SU-2025:15158-1 ## What is CVE-2025-27144? CVE-2025-27144 is a medium-severity denial of service vulnerability in go-jose, published on 24 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling) ## Which versions are affected by CVE-2025-27144? 10 open source packages ship an affected version, including github.com/go-jose/go-jose, github.com/go-jose/go-jose/v3 and github.com/go-jose/go-jose/v4. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/go-jose/go-jose` | Go | All versions | None | | `github.com/go-jose/go-jose` | Go | All versions | 3.0.4 | | `github.com/go-jose/go-jose` | Go | All versions | 3.0.4 | | `github.com/go-jose/go-jose/v3` | Go | All versions | 3.0.4 | | `github.com/go-jose/go-jose/v3` | Go | All versions | 3.0.4 | | `github.com/go-jose/go-jose/v3` | Go | All versions | 3.0.4 | | `github.com/go-jose/go-jose/v4` | Go | All versions | 4.0.5 | | `github.com/go-jose/go-jose/v4` | Go | All versions | 4.0.5 | | `github.com/go-jose/go-jose/v4` | Go | All versions | 4.0.5 | | `github.com/square/go-jose` | Go | All versions | None | | `buildah` | AlmaLinux:10 | All versions | 2:1.39.4-1.el10_0 | | `buildah-tests` | AlmaLinux:10 | All versions | 2:1.39.4-1.el10_0 | | `osbuild-composer` | AlmaLinux:10 | All versions | 134.1-3.el10_0.alma.1 | | `osbuild-composer-core` | AlmaLinux:10 | All versions | 134.1-3.el10_0.alma.1 | | `osbuild-composer-worker` | AlmaLinux:10 | All versions | 134.1-3.el10_0.alma.1 | | `skopeo` | AlmaLinux:10 | All versions | 2:1.18.1-1.el10_0 | | `skopeo-tests` | AlmaLinux:10 | All versions | 2:1.18.1-1.el10_0 | | `buildah` | AlmaLinux:9 | All versions | 2:1.39.4-1.el9_6 | | `buildah-tests` | AlmaLinux:9 | All versions | 2:1.39.4-1.el9_6 | | `skopeo` | AlmaLinux:9 | All versions | 2:1.18.1-1.el9_6 | | `skopeo-tests` | AlmaLinux:9 | All versions | 2:1.18.1-1.el9_6 | | `buildah` | Red Hat:enterprise_linux:10.0 | All versions | 2:1.39.4-1.el10_0 | | `buildah-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 2:1.39.4-1.el10_0 | | `buildah-debugsource` | Red Hat:enterprise_linux:10.0 | All versions | 2:1.39.4-1.el10_0 | | `buildah-tests` | Red Hat:enterprise_linux:10.0 | All versions | 2:1.39.4-1.el10_0 | | `buildah-tests-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 2:1.39.4-1.el10_0 | | `osbuild-composer` | Red Hat:enterprise_linux:10.0 | All versions | 0:134.1-3.el10_0 | | `osbuild-composer-core` | Red Hat:enterprise_linux:10.0 | All versions | 0:134.1-3.el10_0 | | `osbuild-composer-core-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:134.1-3.el10_0 | | `osbuild-composer-debugsource` | Red Hat:enterprise_linux:10.0 | All versions | 0:134.1-3.el10_0 | | `osbuild-composer-tests-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:134.1-3.el10_0 | | `osbuild-composer-worker` | Red Hat:enterprise_linux:10.0 | All versions | 0:134.1-3.el10_0 | | `osbuild-composer-worker-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:134.1-3.el10_0 | | `skopeo` | Red Hat:enterprise_linux:10.0 | All versions | 2:1.18.1-1.el10_0 | | `skopeo-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 2:1.18.1-1.el10_0 | | `skopeo-debugsource` | Red Hat:enterprise_linux:10.0 | All versions | 2:1.18.1-1.el10_0 | | `skopeo-tests` | Red Hat:enterprise_linux:10.0 | All versions | 2:1.18.1-1.el10_0 | | `buildah` | Red Hat:enterprise_linux:9::appstream | All versions | 2:1.39.4-1.el9_6 | | `buildah-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 2:1.39.4-1.el9_6 | | `buildah-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 2:1.39.4-1.el9_6 | ## How do I fix CVE-2025-27144? Upgrade github.com/go-jose/go-jose to 3.0.4 or later. ## Is CVE-2025-27144 being exploited? There is no known exploitation of CVE-2025-27144 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-27144 and fix it if it is affected. What it is: CVE-2025-27144 is a medium-severity denial of service vulnerability in go-jose, published on 24 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-27144 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/go-jose/go-jose (Go): affected all versions; no fix listed - github.com/go-jose/go-jose (Go): affected all versions; fixed in 3.0.4 - github.com/go-jose/go-jose (Go): affected all versions; fixed in 3.0.4 - github.com/go-jose/go-jose/v3 (Go): affected all versions; fixed in 3.0.4 - github.com/go-jose/go-jose/v3 (Go): affected all versions; fixed in 3.0.4 - github.com/go-jose/go-jose/v3 (Go): affected all versions; fixed in 3.0.4 - github.com/go-jose/go-jose/v4 (Go): affected all versions; fixed in 4.0.5 - github.com/go-jose/go-jose/v4 (Go): affected all versions; fixed in 4.0.5 - github.com/go-jose/go-jose/v4 (Go): affected all versions; fixed in 4.0.5 - github.com/square/go-jose (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-27144/ (Markdown: https://insights.sbomify.com/CVE-2025-27144/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27144 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27144 - OSV: https://osv.dev/vulnerability/CVE-2025-27144 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-27144/ Summaries are generated and may contain mistakes; the official description above is the record.