VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

yapi-vendor: vulnerability history, versions and safety

yapi-vendor is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 41 releases, from Nov 2018 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M3
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 23 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all yapi-vendor vulnerabilities

Vulert verdict on yapi-vendor 1.12.0 i

Updated on 23 Oct 2026

Careful: 1.12.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.12.0 — affected i
  • Vulnerabilities on record 4 over 7 years · 1 in the last year i
  • Latest disclosure 23 Feb 2026 i
  • Highest CVSS 7.4 i
  • With no published fix 2 i
  • Stars 27,704 i
  • OpenSSF scorecard 2/10 i
  • Last release 47 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for yapi-vendor, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.12.0 01 Nov 2022 H1 M1 Apache-2.0 No Details →
1.10.2 13 Oct 2021 H1 M1 Apache-2.0 No Details →
1.10.1 30 Aug 2021 H1 M1 Apache-2.0 No Details →
1.9.2 29 May 2020 H1 M2 Apache-2.0 No Details →
1.9.1 28 Apr 2020 H1 M2 Apache-2.0 No Details →
1.9.0 28 Apr 2020 H1 M2 Apache-2.0 No Details →
1.8.8 22 Feb 2020 H1 M2 Apache-2.0 No Details →
1.8.7 06 Feb 2020 H1 M2 Apache-2.0 No Details →
1.8.5 19 Oct 2019 H1 M2 Apache-2.0 No Details →
1.8.4 03 Oct 2019 H1 M2 Apache-2.0 No Details →
1.8.3 26 Aug 2019 H1 M2 Apache-2.0 No Details →
1.8.2 23 Aug 2019 H1 M2 Apache-2.0 No Details →
1.8.1 07 Aug 2019 H1 M2 Apache-2.0 No Details →
1.8.0 23 Jul 2019 H1 M2 Apache-2.0 No Details →
1.7.2 16 Jul 2019 H1 M2 Apache-2.0 No Details →
1.7.1 02 Jul 2019 H1 M2 Apache-2.0 No Details →
1.7.0 26 Apr 2019 H1 M2 Apache-2.0 No Details →
1.7.0-beta.1 26 Apr 2019 H1 M2 Apache-2.0 No Details →
1.5.14 22 Apr 2019 H1 M2 Apache-2.0 No Details →
1.5.13 22 Apr 2019 H1 M2 Apache-2.0 No Details →
1.7.0-beta.0 22 Apr 2019 H1 M2 Apache-2.0 No Details →
1.5.12 21 Apr 2019 H1 M2 Apache-2.0 No Details →
1.6.3 20 Apr 2019 H1 M2 Apache-2.0 No Details →
1.6.2 18 Apr 2019 H1 M2 Apache-2.0 No Details →
1.6.1 18 Apr 2019 H1 M2 Apache-2.0 No Details →
1.6.0 17 Apr 2019 H1 M2 Apache-2.0 No Details →
1.5.11 15 Apr 2019 H1 M2 Apache-2.0 No Details →
1.5.10 30 Mar 2019 H1 M2 Apache-2.0 No Details →
1.5.8 30 Mar 2019 H1 M2 Apache-2.0 No Details →
1.5.7 13 Mar 2019 H1 M2 Apache-2.0 No Details →
1.5.6 22 Feb 2019 H1 M2 Apache-2.0 No Details →
1.5.5 20 Feb 2019 H1 M2 Apache-2.0 No Details →
1.5.4 20 Feb 2019 H1 M2 Apache-2.0 No Details →
1.5.3 20 Feb 2019 H1 M2 Apache-2.0 No Details →
1.5.2 14 Feb 2019 H1 M2 Apache-2.0 No Details →
1.5.1 13 Feb 2019 H1 M2 Apache-2.0 No Details →
1.5.0 30 Jan 2019 H1 M2 Apache-2.0 No Details →
1.4.4 15 Jan 2019 H1 M2 Apache-2.0 No Details →
1.4.3 30 Dec 2018 H1 M2 Apache-2.0 No Details →
1.4.2 30 Dec 2018 H1 M2 Apache-2.0 No Details →
1.4.1 06 Nov 2018 H1 M2 Apache-2.0 No Details →

All 41 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2021 1
  • 2023 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for yapi-vendor

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 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-2018-17574: Cross-site Scripting in yapi-vendor 5.4 medium 1.3.23 21 Nov 2018
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

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About yapi-vendor

Is yapi-vendor safe to use?

Vulert records 4 vulnerabilities for yapi-vendor in npm: 0 critical, 1 high, 3 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is yapi-vendor's Vulert package health score?

Vulert scores yapi-vendor 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of yapi-vendor affected?

Yes. 1.12.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of yapi-vendor should I use?

1.12.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does yapi-vendor have?

4 vulnerabilities are recorded for yapi-vendor in the npm ecosystem: 0 critical, 1 high, 3 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new yapi-vendor vulnerabilities disclosed?

1 vulnerability was recorded for yapi-vendor in the last 12 months, and the oldest entry in this database dates to 21 Nov 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of yapi-vendor are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.