CVE-2023-46809

Node.js versions which bundle an unpatched version of OpenSSL or run against a dynamically linked version of OpenSSL which are unpatched are vulnerable to the Marvin Attack - https://people.redhat.com/~hkario/marvin/, if PCKS #1 v1.5 padding is allowed when performing RSA descryption using a private key.

Published: 2024-09-07 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-46809 is rated Moderate Risk (53/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.30%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-46809

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 1.24% 1.30% +0.06%
2 2026-03-21 1.09% 1.24% +0.14%
3 2026-03-04 — 1.09% —

Full EPSS history (39 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-46809

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.4 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 5.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2023-46809

OS Trackers for CVE-2023-46809

vendor priority summary link
debian not yet assigned CVE-2023-46809 not yet assigned priority: Debian including 1 source packages (nodejs), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2023-46809
gentoo high CVE-2023-46809: 1 GLSA(s) (202505-11), 1 atom(s) (net-libs/nodejs); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2023-46809
redhat medium — https://access.redhat.com/security/cve/CVE-2023-46809
suse medium CVE-2023-46809 severity moderate: SUSE including 71 source package names (18-16.19:nodejs18-18.19.1-150400.9.18.2, 18-16.19:npm18-18.19.1-150400.9.18.2, …), 223 product×package rows across 24 product lines (Container bci/nodejs, SUSE Enterprise Storage 7.1, … (24 product lines)): Fixed 214, Known Not Affected 9. https://www.suse.com/security/cve/CVE-2023-46809/
ubuntu medium CVE-2023-46809 medium priority: Ubuntu including 1 source packages (nodejs), 11 status rows across 11 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 8, ignored 1, needed 1, released 1. https://ubuntu.com/security/CVE-2023-46809

Affected software / configurations for CVE-2023-46809

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2023-46809

cvelogic Threat Intelligence