VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

f2e-server: vulnerability history, versions and safety

f2e-server is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Jul 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all f2e-server vulnerabilities

Vulert verdict on f2e-server 2.20.13 i

Updated on 23 Oct 2026

Good news: 2.20.13, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 53/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on 2.20.13 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.20.13 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.20.13 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 Jul 2018 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 7 packages i
  • Stars 24 i
  • OpenSSF scorecard 1/10 i
  • Last release 37 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 f2e-server, 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
2.20.13 30 Aug 2023 none MIT — Details →
2.20.12 23 Aug 2023 none MIT — Details →
2.20.11 27 Jul 2023 none MIT — Details →
2.20.10 24 May 2023 none MIT — Details →
2.20.9 19 May 2023 none MIT — Details →
2.20.8 19 May 2023 none MIT — Details →
2.20.7 19 May 2023 none MIT — Details →
2.20.6 16 May 2023 none MIT — Details →
2.20.5 15 May 2023 none MIT — Details →
2.20.4 13 May 2023 none MIT — Details →
2.20.3 12 May 2023 none MIT — Details →
2.20.2 12 May 2023 none MIT — Details →
2.20.1 12 May 2023 none MIT — Details →
2.20.0 12 May 2023 none MIT — Details →
2.19.3 06 May 2023 none MIT — Details →
2.19.2 04 May 2023 none MIT — Details →
2.19.1 27 Apr 2023 none MIT — Details →
2.19.0 27 Apr 2023 none MIT — Details →
2.18.8 27 Apr 2023 none MIT — Details →
2.18.7 27 Apr 2023 none MIT — Details →
2.18.6 23 Apr 2023 none MIT — Details →
2.18.5 20 Apr 2023 none MIT — Details →
2.18.4 19 Apr 2023 none MIT — Details →
2.18.3 18 Apr 2023 none MIT — Details →
2.18.2 18 Apr 2023 none MIT — Details →
2.18.1 18 Apr 2023 none MIT — Details →
2.18.0 18 Apr 2023 none MIT — Details →
2.17.5 18 Apr 2023 none MIT — Details →
2.17.4 08 Mar 2023 none MIT — Details →
2.17.3 15 Feb 2023 none MIT — Details →
2.17.2 16 Jan 2023 none MIT — Details →
2.17.1 14 Dec 2022 none MIT — Details →
2.17.0 05 Nov 2022 none MIT — Details →
2.16.17 17 Oct 2022 none MIT — Details →
2.16.16 14 Oct 2022 none MIT — Details →
2.16.15 14 Oct 2022 none MIT — Details →
2.16.14 14 Oct 2022 none MIT — Details →
2.16.13 14 Oct 2022 none MIT — Details →
2.16.12 14 Oct 2022 none MIT — Details →
2.16.11 05 Sep 2022 none MIT — Details →
2.16.10 01 Sep 2022 none MIT — Details →
2.16.9 01 Sep 2022 none MIT — Details →
2.16.8 28 Jun 2022 none MIT — Details →
2.16.7 27 Jun 2022 none MIT — Details →
2.16.6 26 Jun 2022 none MIT — Details →
2.16.5 20 Jun 2022 none MIT — Details →
2.16.4 20 Jun 2022 none MIT — Details →
2.16.3 15 Jun 2022 none MIT — Details →
2.16.2 15 Jun 2022 none MIT — Details →
2.16.1 21 Dec 2021 none MIT — Details →
2.16.0 21 Dec 2021 none MIT — Details →
2.15.2 21 Dec 2021 none MIT — Details →
2.15.1 01 Nov 2021 none MIT — Details →
2.15.0 19 Oct 2021 none MIT — Details →
2.14.14 24 Sep 2021 none MIT — Details →
2.14.13 09 Sep 2021 none MIT — Details →
2.14.12 06 Sep 2021 none MIT — Details →
2.14.10 19 Aug 2021 none MIT — Details →
2.14.9 19 Aug 2021 none MIT — Details →
2.14.8 18 Aug 2021 none MIT — Details →
2.14.6 18 Jun 2021 none MIT — Details →
2.14.5 25 Mar 2021 none MIT — Details →
2.14.4 19 Mar 2021 none MIT — Details →
2.14.3 18 Feb 2021 none MIT — Details →
2.14.2 18 Feb 2021 none MIT — Details →
2.14.1 26 Jan 2021 none MIT — Details →
2.14.0 20 Jan 2021 none MIT — Details →
2.13.7 10 Nov 2020 none MIT — Details →
2.12.19 10 Nov 2020 none MIT — Details →
2.13.6 27 Oct 2020 none MIT — Details →
2.13.5 27 Oct 2020 none MIT — Details →
2.13.4 26 Oct 2020 none MIT — Details →
2.13.3 26 Oct 2020 none MIT — Details →
2.13.2 26 Oct 2020 none MIT — Details →
2.13.1 17 Sep 2020 none MIT — Details →
2.13.0 17 Sep 2020 none MIT — Details →
2.12.18 25 Aug 2020 none MIT — Details →
2.12.17 25 Aug 2020 none MIT — Details →
2.12.16 25 Aug 2020 none MIT — Details →
2.12.15 06 Aug 2020 none MIT — Details →
2.12.14 01 Aug 2020 none MIT — Details →
2.12.13 01 Aug 2020 none MIT — Details →
2.12.11 23 Jul 2020 none MIT — Details →
2.12.10 22 Jul 2020 none MIT — Details →
2.12.9 09 Jun 2020 none MIT — Details →
2.12.8 03 Jun 2020 none MIT — Details →
2.12.7 11 May 2020 none MIT — Details →
2.12.6 23 Apr 2020 none MIT — Details →
2.12.5 24 Dec 2019 none MIT — Details →
2.12.4 24 Dec 2019 none MIT — Details →
2.12.3 19 Dec 2019 none MIT — Details →
2.12.2 19 Dec 2019 none MIT — Details →
2.12.1 18 Dec 2019 none MIT — Details →
2.12.0 18 Dec 2019 none MIT — Details →
2.11.1 10 Dec 2019 none MIT — Details →
2.11.0 04 Dec 2019 none MIT — Details →
2.10.2 11 Sep 2019 none MIT — Details →
2.10.1 22 Jul 2019 none MIT — Details →
2.10.0 09 Jul 2019 none MIT — Details →
2.9.20 31 May 2019 none MIT — Details →
2.9.19 31 May 2019 none — — Details →
2.9.18 30 May 2019 none — — Details →
2.9.17 27 May 2019 none — — Details →
2.9.16 12 Feb 2019 none — — Details →
2.9.15 30 Dec 2018 none — — Details →
2.9.14 30 Dec 2018 none — — Details →
2.9.13 08 Oct 2018 none — — Details →
2.9.12 14 Sep 2018 none — — Details →
2.9.11 13 Aug 2018 none — — Details →
2.9.10 08 Aug 2018 none — — Details →
2.9.9 03 Aug 2018 none — — Details →
2.9.8 12 Jul 2018 none — — Details →
2.9.7 14 Jun 2018 none — — Details →
2.9.6 12 Jun 2018 none — — Details →
2.9.5 07 Jun 2018 none — — Details →
2.9.4 25 May 2018 none — — Details →
2.9.3 22 Apr 2018 none — — Details →
2.9.2 21 Apr 2018 none — — Details →
2.9.1 11 Apr 2018 none — — Details →
2.9.0 11 Apr 2018 none — — Details →

The newest 120 of 330 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1

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

03 Vulnerabilities

Recorded vulnerabilities for f2e-server

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-16038: Directory Traversal in f2e-server 7.5 high 1.12.12 24 Jul 2018

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 f2e-server

Is f2e-server safe to use?

Vulert records 1 vulnerabilities for f2e-server in npm: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is f2e-server's Vulert package health score?

Vulert scores f2e-server 53/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).

Is the latest version of f2e-server affected?

No. 2.20.13, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of f2e-server should I use?

2.20.13 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 f2e-server have?

1 vulnerability is recorded for f2e-server in the npm ecosystem: 0 critical, 1 high, 0 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 f2e-server vulnerabilities disclosed?

0 vulnerabilities were recorded for f2e-server in the last 12 months, and the oldest entry in this database dates to 24 Jul 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 f2e-server 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 f2e-server for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the f2e-server version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.