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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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 pinpoints whether GHSA-2c7c-3mj9-8fqh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 February 4, 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

GHSA-2c7c-3mj9-8fqh

GHSA-2c7c-3mj9-8fqh is a security vulnerability in github.com/go-jose/go-jose/v3. O3 Security confirms whether GHSA-2c7c-3mj9-8fqh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Decryption of malicious PBES2 JWE objects can consume unbounded system resources

Also known asGO-2023-2334

Published

Nov 21, 2023

Updated

Feb 4, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

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	`github.com/square/go-jose`	all versions	2.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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether GHSA-2c7c-3mj9-8fqh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 detects GHSA-2c7c-3mj9-8fqh across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works