How severe is CVE-2025-27144?

No CVSS score has been assigned to CVE-2025-27144 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-27144?

CVE-2025-27144 affects the following packages: github.com/go-jose/go-jose/v4 (Go), github.com/go-jose/go-jose/v3 (Go), github.com/go-jose/go-jose (Go). Ecosystems affected: Go.

How do I fix CVE-2025-27144?

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.

How do I detect CVE-2025-27144 in my Go dependencies?

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.

How do I mitigate CVE-2025-27144 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-27144?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-27144 can be triaged on real exposure rather than presence alone.

Is CVE-2025-27144 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-27144 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-27144?

CVE-2025-27144 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-27144?

CVE-2025-27144 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-27144 published, and has it been updated?

CVE-2025-27144 was published on February 24, 2025 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-27144 — v4

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

Feb 24, 2025

Updated

Aug 12, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 24, 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 CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/go-jose/go-jose/v4`	all versions	4.0.5`go get github.com/go-jose/go-jose/v4@v4.0.5`
🐹Go	`github.com/go-jose/go-jose/v3`	all versions	3.0.4`go get github.com/go-jose/go-jose/v3@v3.0.4`
🐹Go	`github.com/go-jose/go-jose`	all versions	3.0.4`go get github.com/go-jose/go-jose@v3.0.4`

Detection & mitigation playbook

Open-source dependency

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.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-27144 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-27144. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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

Product	Fixed in	Advisory
OADP-1.4-RHEL-9	`oadp/oadp-mustgather-rhel9:1.4.5-34`	RHSA-2025:11396
Red Hat Advanced Cluster Security 4.6	`advanced-cluster-security/rhacs-central-db-rhel8:4.6.4-4`	RHSA-2025:3439
Red Hat Advanced Cluster Security 4.7	`advanced-cluster-security/rhacs-central-db-rhel8:4.7.1-2`	RHSA-2025:3438
Red Hat Enterprise Linux 10	`osbuild-composer-0:134.1-3.el10_0`	RHSA-2025:19566
Red Hat Enterprise Linux 10	`buildah-2:1.39.4-1.el10_0`	RHSA-2025:7459
Red Hat Enterprise Linux 10	`podman-6:5.4.0-9.el10_0`	RHSA-2025:7462
Red Hat Enterprise Linux 10	`skopeo-2:1.18.1-1.el10_0`	RHSA-2025:7467
Red Hat Enterprise Linux 10	`opentelemetry-collector-0:0.107.0-9.el10_0`	RHSA-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?

O3 Security finds CVE-2025-27144 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works