Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-86r9-39j9-99wp

CRITICAL

GHSA-86r9-39j9-99wp is a critical-severity (CVSS 9.1) CWE-326 vulnerability in gopkg.in/square/go-jose.v1. O3 Security confirms whether GHSA-86r9-39j9-99wp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Elliptic Curve Key Disclosure in go-jose

Also known asCVE-2016-9121GO-2020-0010
Published
Jun 23, 2021
Updated
Nov 8, 2023
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected
🐹gopkg.in/square/go-jose.v1🐹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

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

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogopkg.in/square/go-jose.v1all versions1.0.4
🐹Gogithub.com/square/go-joseall versions1.0.4

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gopkg.in/square/go-jose.v1. 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.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-86r9-39j9-99wp 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-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

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.
O3 Security · Impact-Aware SCA

Is GHSA-86r9-39j9-99wp in your dependencies?

O3 detects GHSA-86r9-39j9-99wp across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.