GHSA-86r9-39j9-99wp is a critical-severity (CVSS 9.1) CWE-326 vulnerability in gopkg.in/square/go-jose.v1. A fix is available for gopkg.in/square/go-jose.v1 — see the affected versions and patch details below.
Elliptic Curve Key Disclosure in go-jose
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-86r9-39j9-99wp plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
gopkg.in/square/go-jose.v1🐹github.com/square/go-joseReal-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 before 1.0.4 suffers from an invalid curve attack for the ECDH-ES algorithm. When deriving a shared key using ECDH-ES for an encrypted message, go-jose neglected to check that the received public key on a message is on the same curve as the static private key of the receiver, thus making it vulnerable to an invalid curve attack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | gopkg.in/square/go-jose.v1 | all versions | 1.0.4go get gopkg.in/square/go-jose.v1@v1.0.4 |
| 🐹Go | github.com/square/go-jose | all versions | 1.0.4go get github.com/square/go-jose@v1.0.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gopkg.in/square/go-jose.v1, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update gopkg.in/square/go-jose.v1 to 1.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-86r9-39j9-99wp 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-86r9-39j9-99wp can be triaged on real exposure rather than presence alone.
Tailored to GHSA-86r9-39j9-99wp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-86r9-39j9-99wp in your dependencies?
O3 Security finds GHSA-86r9-39j9-99wp across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.