Vulnerability Database · npm · openssl · Version
openssl 2.0.0
2.0.0 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 16 Nov 2021
Status latest release
Licence ISC
Also known from other sources 1
Newer releases 5
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
openssl 2.0.0 vulnerabilities
1 vulnerability cover openssl 2.0.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2023-49210: openssl npm package vulnerable to command execution | 9.8 critical | No fix published | 23 Nov 2023 |
Looking for another version, or everything Vulert holds for openssl?
Questions
About openssl 2.0.0
Is openssl 2.0.0 vulnerable?
Yes. 1 vulnerability in the Vulert database cover openssl 2.0.0: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 2.0.0 the latest release of openssl?
Yes. 2.0.0 is the current release, published 16 Nov 2021. Staying on the current line is what keeps you inside the publisher's fixes.
How do I monitor openssl for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the openssl version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.