Vulnerability Database · npm · libxmljs2 · Version
libxmljs2 0.26.6
0.26.6 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 0.37.0.
Critical 2 High 0 Medium 0 Low 0 Unrated 0
-
Released 04 Jan 2021
Licence MIT
Also known from other sources 2
Newer releases 38
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
libxmljs2 0.26.6 vulnerabilities
2 vulnerabilities cover libxmljs2 0.26.6. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2024-34393: libxmljs2 Type Confusion Vulnerability | 8.1 critical | No fix published | 02 May 2024 |
| CVE-2024-34394: libxmljs2 vulnerable to type confusion when parsing specially crafted XML | 8.1 critical | No fix published | 02 May 2024 |
Looking for another version, or everything Vulert holds for libxmljs2?
Questions
About libxmljs2 0.26.6
Is libxmljs2 0.26.6 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover libxmljs2 0.26.6: 2 critical, 0 high, 0 medium and 0 low. The upgrade Vulert recommends is 0.37.0, and each entry above names the fixed version to move to.
Which version of libxmljs2 should I use instead of 0.26.6?
0.37.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.26.6 the latest release of libxmljs2?
No. 0.26.6 was published 04 Jan 2021, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor libxmljs2 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the libxmljs2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.