How severe is CVE-2023-46809?

CVE-2023-46809 has a CVSS 3.x base score of 7.4, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2023-46809 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2023-46809?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2023-46809 have an EU (EUVD) identifier?

Yes. CVE-2023-46809 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2023-50975.

When was CVE-2023-46809 published?

CVE-2023-46809 was published on 2024-09-07 and last updated on 2026-06-17.

CVE-2023-46809

CVE-2023-46809 is a high-severity vulnerability with a CVSS 3.x base score of 7.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-385.

Key facts

Severity: High (CVSS 3.x base score 7.4)
EPSS exploit prediction: 1% (67th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2023-50975
Weakness: CWE-385
Published: 2024-09-07
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is 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.
How severe is CVE-2023-46809?: CVE-2023-46809 has a CVSS 3.x base score of 7.4, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2023-46809 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2023-46809?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2023-46809 have an EU (EUVD) identifier?: Yes. CVE-2023-46809 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2023-50975.
When was CVE-2023-46809 published?: CVE-2023-46809 was published on 2024-09-07 and last updated on 2026-06-17.

References

Other CWE-385 vulnerabilities

CVE-2026-5598 — High (CVSS 7.5): Covert timing channel vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA core on all (core modules). This…
CVE-2025-59425 — High (CVSS 7.5): vLLM is an inference and serving engine for large language models (LLMs). Before version 0.11.0rc2, the API key support…
CVE-2020-25658 — High (CVSS 7.5): It was found that python-rsa is vulnerable to Bleichenbacher timing attacks. An attacker can use this flaw via the RSA…
CVE-2025-0306 — High (CVSS 7.4): A vulnerability was found in Ruby. The Ruby interpreter is vulnerable to the Marvin Attack. This attack allows the…
CVE-2023-3640 — High (CVSS 7.0): A possible unauthorized memory access flaw was found in the Linux kernel's cpu_entry_area mapping of X86 CPU data to…
CVE-2020-29506 — Medium (CVSS 6.8): Dell BSAFE Crypto-C Micro Edition, versions before 4.1.5, and Dell BSAFE Micro Edition Suite, versions before 4.5.2,…

Browse all CWE-385 vulnerabilities →