CVE-2016-9121

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering.

Exploit odds

1.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2017-03-28 02:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:55 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.4% in the next 30 days (EPSS).
• Severity: 9.1 CRITICAL (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2017-03-28 02:59 UTC

Last modified

2026-06-17 00:55 UTC

Exploit probability

1.4% · EPSS, next 30 days

Weakness

CWE-326 · Inadequate encryption strength

Record status

Modified

Affected

• go-jose Project go-jose ≤ 1.0.3

Attack profile CVSS 3.0 · 9.1

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-9121.md and follow it. Check whether this project is affected by CVE-2016-9121. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge