How severe is GHSA-2c7c-3mj9-8fqh?

No CVSS score has been assigned to GHSA-2c7c-3mj9-8fqh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2c7c-3mj9-8fqh?

GHSA-2c7c-3mj9-8fqh affects the following packages: github.com/go-jose/go-jose/v3 (Go), github.com/square/go-jose (Go). Ecosystems affected: Go.

How do I fix GHSA-2c7c-3mj9-8fqh?

Update github.com/go-jose/go-jose/v3 to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2c7c-3mj9-8fqh is resolved across your whole dependency graph.

How do I detect GHSA-2c7c-3mj9-8fqh 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/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2c7c-3mj9-8fqh 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 GHSA-2c7c-3mj9-8fqh?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2c7c-3mj9-8fqh can be triaged on real exposure rather than presence alone.

Is GHSA-2c7c-3mj9-8fqh actively exploited in the wild?

No public exploit code has been indexed for GHSA-2c7c-3mj9-8fqh 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.

When was GHSA-2c7c-3mj9-8fqh published, and has it been updated?

GHSA-2c7c-3mj9-8fqh was published on November 21, 2023 and was last updated on September 10, 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

GHSA-2c7c-3mj9-8fqh — v3

Fix: go-jose/go-jose@65351c2

GHSA-2c7c-3mj9-8fqh is a security vulnerability in github.com/go-jose/go-jose/v3. A fix is available for github.com/go-jose/go-jose/v3 — see the affected versions and patch details below.

Decryption of malicious PBES2 JWE objects can consume unbounded system resources

Also known asGO-2023-2334

Published

Nov 21, 2023

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐹github.com/go-jose/go-jose/v3🐹github.com/square/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

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/go-jose/go-jose/v3`	all versions	3.0.1`go get github.com/go-jose/go-jose/v3@v3.0.1`
🐹Go	`github.com/square/go-jose`	all versions	2.6.2`go get github.com/square/go-jose@v2.6.2`

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/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/go-jose/go-jose/v3 to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2c7c-3mj9-8fqh 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 GHSA-2c7c-3mj9-8fqh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2c7c-3mj9-8fqh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-2c7c-3mj9-8fqh in your dependencies?

O3 Security finds GHSA-2c7c-3mj9-8fqh 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