What is GHSA-2C7C-3MJ9-8FQH?

GHSA-2C7C-3MJ9-8FQH is a medium-severity uncontrolled resource consumption vulnerability in github.com/go-jose/go-jose/v3 (go), affecting versions < 3.0.1. It is fixed in 3.0.1, 2.6.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

Which packages are affected by GHSA-2C7C-3MJ9-8FQH?

github.com/go-jose/go-jose/v3 (go) versions < 3.0.1; github.com/square/go-jose (go) versions < 2.6.2.

Is there a fix for GHSA-2C7C-3MJ9-8FQH?

Yes. GHSA-2C7C-3MJ9-8FQH is fixed in 3.0.1, 2.6.2. Upgrade to this version or later.

Is GHSA-2C7C-3MJ9-8FQH exploitable, and should I be worried?

Whether GHSA-2C7C-3MJ9-8FQH 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.

What actually determines whether GHSA-2C7C-3MJ9-8FQH 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.

GHSA-2C7C-3MJ9-8FQH in github.com/go-jose/go-jose/v3

Q: Which packages are affected by GHSA-2C7C-3MJ9-8FQH?

github.com/go-jose/go-jose/v3 (go) versions < 3.0.1; github.com/square/go-jose (go) versions < 2.6.2.

Q: Is there a fix for GHSA-2C7C-3MJ9-8FQH?

Yes. GHSA-2C7C-3MJ9-8FQH is fixed in 3.0.1, 2.6.2. Upgrade to this version or later.

Q: Is GHSA-2C7C-3MJ9-8FQH exploitable, and should I be worried?

Whether GHSA-2C7C-3MJ9-8FQH 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.

Q: What actually determines whether GHSA-2C7C-3MJ9-8FQH 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.

Q: How do I fix GHSA-2C7C-3MJ9-8FQH?

Upgrade: github.com/go-jose/go-jose/v3 to 3.0.1 or later, github.com/square/go-jose to 2.6.2 or later.

Summary

Decryption of malicious PBES2 JWE objects can consume unbounded system resources

The go-jose package is subject to a "billion hashes attack" causing denial-of-service when decrypting JWE inputs. This occurs when an attacker can provide a PBES2 encrypted JWE blob with a very large p2c value that, when decrypted, produces a denial-of-service.

Impact

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

Affected versions

github.com/go-jose/go-jose/v3 (< 3.0.1) github.com/square/go-jose (< 2.6.2)

Security releases

github.com/go-jose/go-jose/v3 → 3.0.1 (go) github.com/square/go-jose → 2.6.2 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

github.com/go-jose/go-jose/v3 to 3.0.1 or later; github.com/square/go-jose to 2.6.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-2C7C-3MJ9-8FQH? GHSA-2C7C-3MJ9-8FQH is a medium-severity uncontrolled resource consumption vulnerability in github.com/go-jose/go-jose/v3 (go), affecting versions < 3.0.1. It is fixed in 3.0.1, 2.6.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
Which packages are affected by GHSA-2C7C-3MJ9-8FQH?
- github.com/go-jose/go-jose/v3 (go) (versions < 3.0.1)
- github.com/square/go-jose (go) (versions < 2.6.2)
Is there a fix for GHSA-2C7C-3MJ9-8FQH? Yes. GHSA-2C7C-3MJ9-8FQH is fixed in 3.0.1, 2.6.2. Upgrade to this version or later.
Is GHSA-2C7C-3MJ9-8FQH exploitable, and should I be worried? Whether GHSA-2C7C-3MJ9-8FQH 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
What actually determines whether GHSA-2C7C-3MJ9-8FQH 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.
How do I fix GHSA-2C7C-3MJ9-8FQH?
- Upgrade github.com/go-jose/go-jose/v3 to 3.0.1 or later
- Upgrade github.com/square/go-jose to 2.6.2 or later

Other vulnerabilities in github.com/go-jose/go-jose/v3

CVE-IDSeverityPackage summary

CVE-2026-34986Highgithub.com/go-jose/go-jose/v4: Go JOSE Panics in JWE decryption CVE-2025-27144Mediumgithub.com/go-jose/go-jose/v4: DoS in go-jose Parsing CVE-2024-28180Mediumgithub.com/go-jose/go-jose/v4: Go JOSE vulnerable to Improper Handling of Highly Compressed Data (Data Amplification)