VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

console-io: vulnerability history, versions and safety

console-io is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 15 releases, first recorded in Feb 2019. 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 C1
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 console-io vulnerabilities

Vulert verdict on console-io 15.0.4 i

Updated on 22 Oct 2026

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

Package health score 62/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Inactive

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

  • Current release 15.0.4 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 18 Feb 2019 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Stars 59 i
  • OpenSSF scorecard 2/10 i
  • Last release 6 months ago i
  • Licence MIT 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 console-io, 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
15.0.4 29 Mar 2026 none MIT — Details →
15.0.3 18 Feb 2026 none MIT — Details →
15.0.2 10 Feb 2026 none MIT — Details →
15.0.1 10 Feb 2026 none MIT — Details →
15.0.0 10 Feb 2026 none MIT — Details →
14.1.0 12 Oct 2023 none MIT — Details →
14.0.1 10 Aug 2023 none MIT — Details →
14.0.0 10 Aug 2023 none MIT — Details →
13.0.2 20 Jan 2021 none MIT — Details →
13.0.1 19 Jan 2021 none MIT — Details →
13.0.0 19 Jan 2021 none MIT — Details →
12.0.1 16 Nov 2020 none MIT — Details →
12.0.0 16 Nov 2020 none MIT — Details →
11.0.2 21 Sep 2020 none MIT — Details →
11.0.1 08 Nov 2019 none MIT — Details →
11.0.0 21 Sep 2019 none MIT — Details →
10.1.3 19 Sep 2019 none MIT — Details →
10.1.2 19 Sep 2019 none MIT — Details →
10.1.1 09 Sep 2019 none MIT — Details →
10.1.0 06 Sep 2019 none MIT — Details →
10.0.7 21 Aug 2019 none MIT — Details →
10.0.6 21 Aug 2019 none MIT — Details →
10.0.5 11 Jul 2019 none MIT — Details →
10.0.4 11 Jul 2019 none MIT — Details →
10.0.3 15 May 2019 none MIT — Details →
10.0.2 15 Apr 2019 none MIT — Details →
10.0.1 14 Nov 2018 none MIT — Details →
10.0.0 25 Oct 2018 none MIT — Details →
9.1.0 23 Oct 2018 none MIT — Details →
9.0.1 22 Oct 2018 none MIT — Details →
9.0.0 19 Oct 2018 none MIT — Details →
8.1.3 19 Oct 2018 none MIT — Details →
8.1.2 19 Oct 2018 none MIT — Details →
8.1.1 19 Oct 2018 none MIT — Details →
8.1.0 19 Oct 2018 none MIT — Details →
8.0.4 19 Oct 2018 none MIT — Details →
8.0.3 10 Oct 2018 none MIT — Details →
8.0.2 02 Oct 2018 none MIT — Details →
8.0.1 02 Oct 2018 none MIT — Details →
8.0.0 27 Sep 2018 none MIT — Details →
7.0.6 10 May 2018 none MIT — Details →
7.0.5 03 May 2018 none MIT — Details →
7.0.4 26 Apr 2018 none MIT — Details →
7.0.3 02 Apr 2018 none MIT — Details →
7.0.2 30 Mar 2018 none MIT — Details →
7.0.1 30 Mar 2018 none MIT — Details →
7.0.0 30 Mar 2018 none MIT — Details →
6.0.1 20 Mar 2018 none MIT — Details →
6.0.0 20 Mar 2018 none MIT — Details →
5.1.0 19 Mar 2018 none MIT — Details →
5.0.6 05 Mar 2018 none MIT — Details →
5.0.5 01 Mar 2018 none MIT — Details →
5.0.4 05 Dec 2017 none MIT — Details →
5.0.3 25 Jul 2017 none MIT — Details →
5.0.2 25 Jul 2017 none MIT — Details →
5.0.1 13 Jul 2017 none MIT — Details →
5.0.0 12 Jul 2017 none MIT — Details →
4.0.0 04 Jul 2017 none MIT — Details →
3.1.3 21 Jun 2017 none MIT — Details →
3.1.2 14 Jun 2017 none MIT — Details →
3.1.1 14 Jun 2017 none MIT — Details →
3.1.0 26 May 2017 none MIT — Details →
3.0.13 10 May 2017 none MIT — Details →
3.0.12 10 May 2017 none MIT — Details →
3.0.11 02 Mar 2017 none MIT — Details →
3.0.10 01 Mar 2017 none MIT — Details →
3.0.9 08 Feb 2017 none MIT — Details →
3.0.8 19 Dec 2016 none MIT — Details →
3.0.7 19 Dec 2016 none MIT — Details →
3.0.6 23 Nov 2016 none MIT — Details →
3.0.5 21 Nov 2016 none MIT — Details →
3.0.4 17 Nov 2016 none MIT — Details →
3.0.3 17 Nov 2016 none MIT — Details →
3.0.2 16 Nov 2016 none MIT — Details →
3.0.1 15 Nov 2016 none MIT — Details →
3.0.0 15 Nov 2016 none MIT — Details →
2.7.14 09 Nov 2016 none MIT — Details →
2.7.13 26 Oct 2016 none MIT — Details →
2.7.12 25 Oct 2016 none MIT — Details →
2.7.11 20 Oct 2016 none MIT — Details →
2.7.10 08 Oct 2016 none MIT — Details →
2.7.9 23 Sep 2016 none MIT — Details →
2.7.8 12 Jul 2016 none MIT — Details →
2.7.7 17 Jun 2016 none MIT — Details →
2.7.6 14 Jun 2016 none MIT — Details →
2.7.5 13 Apr 2016 none MIT — Details →
2.7.4 22 Mar 2016 none MIT — Details →
2.7.3 17 Mar 2016 none MIT — Details →
2.7.2 17 Mar 2016 none MIT — Details →
2.7.1 17 Mar 2016 none MIT — Details →
2.7.0 17 Mar 2016 none MIT — Details →
2.6.3 17 Mar 2016 none MIT — Details →
2.6.2 01 Feb 2016 none MIT — Details →
2.6.1 01 Feb 2016 none MIT — Details →
2.6.0 31 Jan 2016 none MIT — Details →
2.5.3 28 Jan 2016 none MIT — Details →
2.5.2 10 Jan 2016 none MIT — Details →
2.5.1 27 Nov 2015 none MIT — Details →
2.5.0 11 Nov 2015 none MIT — Details →
2.4.1 09 Nov 2015 none MIT — Details →
2.4.0 04 Nov 2015 none — — Details →
2.3.3 21 Oct 2015 none — — Details →
2.3.2 21 Oct 2015 none — — Details →
2.3.1 14 Oct 2015 none — — Details →
2.3.0 29 Sep 2015 none — — Details →
2.2.13 21 Sep 2015 C1 — Yes Details →
2.2.12 19 Aug 2015 C1 — Yes Details →
2.2.11 20 Jul 2015 C1 — Yes Details →
2.2.10 21 Jun 2015 C1 — Yes Details →
2.2.9 04 Jun 2015 C1 — Yes Details →
2.2.8 02 Jun 2015 C1 — Yes Details →
2.2.7 21 May 2015 C1 — Yes Details →
2.2.6 13 May 2015 C1 — Yes Details →
2.2.5 12 May 2015 C1 — Yes Details →
2.2.4 17 Mar 2015 C1 — Yes Details →
2.2.3 13 Mar 2015 C1 — Yes Details →
2.2.2 01 Mar 2015 C1 — Yes Details →
2.2.1 01 Mar 2015 C1 — Yes Details →
2.2.0 24 Feb 2015 C1 — Yes Details →
2.1.15 16 Feb 2015 C1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 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 console-io

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-10532: Authentication Bypass in console-io 9.8 critical 2.3.0 18 Feb 2019

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 console-io

Is console-io safe to use?

Vulert records 1 vulnerabilities for console-io in npm: 1 critical, 0 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 console-io's Vulert package health score?

Vulert scores console-io 62/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 console-io affected?

No. 15.0.4, 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 console-io should I use?

15.0.4 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 console-io have?

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

0 vulnerabilities were recorded for console-io in the last 12 months, and the oldest entry in this database dates to 18 Feb 2019. 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 console-io 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 console-io for upcoming vulnerabilities?

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