Vulnerability Database · npm · yapi-vendor · Version
yapi-vendor 1.5.7
1.5.7 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.12.0.
Critical 0 High 1 Medium 2 Low 0 Unrated 0
-
Released 13 Mar 2019
Licence Apache-2.0
Also known from other sources 3
Newer releases 41
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
yapi-vendor 1.5.7 vulnerabilities
3 vulnerabilities cover yapi-vendor 1.5.7. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2025-70058: yapi-vendor Package Disables TLS/SSL Certificate Validation | 7.4 high | No fix published | 23 Feb 2026 |
| CVE-2021-36686: Cross-site Scripting in yapi-vendor | 5.4 medium | No fix published | 26 Jan 2023 |
| CVE-2021-27884: Weak JSON Web Token in yapi-vendor | 5.1 medium | 1.9.3 | 26 Mar 2021 |
Looking for another version, or everything Vulert holds for yapi-vendor?
Questions
About yapi-vendor 1.5.7
Is yapi-vendor 1.5.7 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover yapi-vendor 1.5.7: 0 critical, 1 high, 2 medium and 0 low. The upgrade Vulert recommends is 1.12.0, and each entry above names the fixed version to move to.
Which version of yapi-vendor should I use instead of 1.5.7?
1.12.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 1.5.7 the latest release of yapi-vendor?
No. 1.5.7 was published 13 Mar 2019, 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 yapi-vendor for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the yapi-vendor version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.