Skip to main content
Mallory
HighVulnerability

CVE-2023-30590: Node.js Diffie-Hellman Key Generation Documentation Mismatch

Published Nov 28, 2023 · Updated 10 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 2 in a dayToday
CVSS7.5High · v3.1
EPSS1.5%74th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Nodejs
IdentifiersCVE-2023-30590CWE-440

CVE-2023-30590 is a discrepancy between the documented and actual behavior of generateKeys() on DiffieHellman objects created by Node.js crypto.createDiffieHellman(). Although the documentation states that the method generates private and public Diffie-Hellman key values, the implementation generates only missing or outdated keys and generates a private key only if none has already been set. The method is also used to compute the corresponding public key after setPrivateKey(), so calling it does not necessarily create a fresh key pair. Applications relying on the documented behavior can consequently make incorrect assumptions about key generation and renewal, undermining application-level security. Affected maintained branches at disclosure included Node.js 16 before 16.20.1, 18 before 18.16.1, and 20 before 20.3.1; older release lines were also affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Applications that incorrectly assume generateKeys() replaces an existing private key may retain key material they intended to renew, potentially compromising the integrity guarantees of application-level cryptographic protocols. Weak or predictable shared secrets have been identified as a theoretical consequence, but the actual impact depends on application logic and key handling. This is a developer-facing API documentation hazard rather than an independently exploitable cryptographic primitive failure. The assigned CVSS v3.1 score is 7.5, with high integrity impact and no assessed confidentiality or availability impact.

Mitigation

If you can’t patch tonight, do this now.

Audit Diffie-Hellman key lifecycle logic, particularly calls to generateKeys() on objects with an existing private key. Do not treat that call as proof that a fresh private key was generated. Where fresh keys are required, explicitly implement and verify fresh key generation rather than relying on repeated calls on an already initialized object. No vendor-specific temporary workaround is identified.

Remediation

Patch, then assume compromise.

Install vendor-provided Node.js updates addressing CVE-2023-30590 and use a currently supported release. The original upstream update thresholds were 16.20.1, 18.16.1, and 20.3.1; distribution packages may contain backported fixes. Debian fixes include 10.24.0~dfsg-1~deb10u4 for Debian 10 and 12.22.12~dfsg-1~deb11u5 for Debian 11. The correction aligns the documentation with the existing implementation rather than making generateKeys() unconditionally regenerate keys. Review and correct application code that relies on the former documentation, since updating Node.js alone does not repair those assumptions.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
NodejsNodejsapplication
FAQ

Frequently asked questions

Is CVE-2023-30590 exploited in the wild?
As of Nov 7, 2026, Mallory has no reports of CVE-2023-30590 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2023-30590?
As of Nov 7, 2026, Mallory has found no public exploit for CVE-2023-30590.
Is there a patch for CVE-2023-30590?
Install vendor-provided Node.js updates addressing CVE-2023-30590 and use a currently supported release. The original upstream update thresholds were 16.20.1, 18.16.1, and 20.3.1; distribution packages may contain backported fixes.
What products are affected by CVE-2023-30590?
Nodejs.
How severe is CVE-2023-30590?
CVE-2023-30590 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.5% (74th percentile) as of Nov 7, 2026.
Activity feed

Recent activity

15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 7, 2026Rocky Linux 9 [CIQ] Security Update: nodejs-packaging / nodejs... | Tenable®A Node.js DiffieHellman key-generation vulnerability involving setting a private key. The plugin identifies this CVE as its CVSS score source, reports exploit availability, and provides a proof-of-concept exploit-maturity rating. Affected Rocky Linux 9 packages require the updates identified in CIQ advisory crlsa-2023_4330.Read more ↗tenable nessus pluginsNews · Nov 6, 2026RockyLinux 9 : nodejs:18 (RLSA-2023:4330) | Tenable®A Node.js vulnerability involving DiffieHellman key generation after a private key has been set. The finding uses this CVE as its CVSS score source, with a vector indicating high integrity impact. Updated packages are available under Rocky Linux advisory RLSA-2023:4330. Exploit availability is reported for the combined advisory finding without explicit per-CVE attribution.Read more ↗tenable nessus pluginsNews · Nov 2, 2026Unity Linux 20.1050a / 20.1060a / 20.1070a Security Update: no... | Tenable®A discrepancy between documented and actual behavior in Node.js Diffie-Hellman key generation can undermine application-level security. generateKeys() does not necessarily generate a new private key when one already exists, potentially violating applications' security assumptions. The advisory identifies affected nodejs packages on Unity Linux 20.1050a, 20.1060a, and 20.1070a. The listed CVSS v3 base score is 7.5, reflecting high integrity impact. Nessus checks the reported package version rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Nov 2, 2026Unity Linux 20.1050a / 20.1060a / 20.1070a Security Update: no... | Tenable®A discrepancy between documented and actual Node.js Diffie-Hellman key-generation behavior can undermine application-level security. generateKeys() does not generate a new private key when one is already set, potentially violating applications' security assumptions. The advisory identifies affected nodejs packages on Unity Linux and recommends updating them. The listed CVSS v3 base score is 7.5. Nessus checks the application's reported version rather than testing the vulnerability directly.Read more ↗
+10 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.