NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2020-36843 — eddsa

MEDIUMFix: i2p/i2p.i2p@d7d1dcb

CVE-2020-36843 is a medium-severity (CVSS 4.3) CWE-347 vulnerability in net.i2p.crypto:eddsa. A fix is available for net.i2p.crypto:eddsa — see the affected versions and patch details below.

Ed25519 Signature Malleability in ed25519-java Due to Missing Scalar Range Check

Also known asGHSA-p53j-g8pw-4w5f
Published
Updated
Affected
2 pkgs
Patched
1 / 2
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2020-36843.

EPSS Exploitation Probability

via FIRST.org ↗
0.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs4th percentile — riskier than 4% of all scored CVEsHighest risk
0.00%0.21%0.43%0.64%0.0%0.1%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕net.i2p.crypto:eddsa☕net.i2p:i2p

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The implementation of EdDSA in EdDSA-Java (aka ed25519-java) through 0.3.0 exhibits signature malleability and does not satisfy the SUF-CMA (Strong Existential Unforgeability under Chosen Message Attacks) property. This allows attackers to create new valid signatures different from previous signatures for a known message.

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavennet.i2p.crypto:eddsaall versionsNo fix
☕Mavennet.i2p:i2pall versions0.9.39net.i2p:i2p:0.9.39

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.i2p.crypto:eddsa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    A fix is available for CVE-2020-36843; check the affected-versions list above or the advisory for the patched release of net.i2p.crypto:eddsa, then make sure no transitive dependency still pins the vulnerable range.

  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.

Frequently Asked Questions

The implementation of EdDSA in EdDSA-Java (aka ed25519-java) through 0.3.0 exhibits signature malleability and does not satisfy the SUF-CMA (Strong Existential Unforgeability under Chosen Message Attacks) property. This allows attackers to create new valid signatures different from previous signatures for a known message.
O3 Security · Impact-Aware SCA

Is CVE-2020-36843 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2020-36843: eddsa — Fixed in 0.9.39