NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹 Go
Not in CISA KEV

CVE-2025-27144 — go-jose

Fix: go-jose/go-jose@99b346c

CVE-2025-27144 is a CWE-770 vulnerability in github.com/go-jose/go-jose/v4. A fix is available for github.com/go-jose/go-jose/v4 — see the affected versions and patch details below.

Go JOSE's Parsing Vulnerable to Denial of Service

Also known asGHSA-c6gw-w398-hv78GO-2025-3485
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-27144.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs34th percentile — riskier than 34% of all scored CVEsHighest risk
0.00%0.30%0.60%0.90%0.1%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected
🐹github.com/go-jose/go-jose/v4🐹github.com/go-jose/go-jose/v3🐹github.com/go-jose/go-jose

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/go-jose/go-jose/v4all versions4.0.5go get github.com/go-jose/go-jose/v4@v4.0.5
🐹Gogithub.com/go-jose/go-jose/v3all versions3.0.4go get github.com/go-jose/go-jose/v3@v3.0.4
🐹Gogithub.com/go-jose/go-joseall versions3.0.4go get github.com/go-jose/go-jose@v3.0.4

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/go-jose/go-jose/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/go-jose/go-jose/v4 to 4.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-27144 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

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…

Workaround published by Red Hat
As a workaround, applications can pre-validate that payloads being passed to Go JOSE do not contain an excessive number of `.` characters.
Source: Red Hat security advisory for CVE-2025-27144 (CC BY 4.0)
ProductFixed inAdvisory
OADP-1.4-RHEL-9oadp/oadp-mustgather-rhel9:1.4.5-34RHSA-2025:11396
Red Hat Advanced Cluster Security 4.6advanced-cluster-security/rhacs-central-db-rhel8:4.6.4-4RHSA-2025:3439
Red Hat Advanced Cluster Security 4.7advanced-cluster-security/rhacs-central-db-rhel8:4.7.1-2RHSA-2025:3438
Red Hat Enterprise Linux 10osbuild-composer-0:134.1-3.el10_0RHSA-2025:19566
Red Hat Enterprise Linux 10buildah-2:1.39.4-1.el10_0RHSA-2025:7459
Red Hat Enterprise Linux 10podman-6:5.4.0-9.el10_0RHSA-2025:7462
Red Hat Enterprise Linux 10skopeo-2:1.18.1-1.el10_0RHSA-2025:7467
Red Hat Enterprise Linux 10opentelemetry-collector-0:0.107.0-9.el10_0RHSA-2025:7479

Frequently Asked Questions

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 malfor
O3 Security · Impact-Aware SCA

Is CVE-2025-27144 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2025-27144: go-jose DoS — Fixed in 4.0.5