VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

aegir: vulnerability history, versions and safety

aegir is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 0 release, from Jul 2018 to May 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 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 aegir vulnerabilities

Vulert verdict on aegir 48.1.6 i

Updated on 23 Oct 2026

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

Package health score 69/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 48.1.6 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 27 May 2020 i
  • Highest CVSS 9.6 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Stars 105 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 OR 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 aegir, 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
48.1.6 27 Aug 2026 none Apache-2.0 OR MIT — Details →
48.1.5 26 Aug 2026 none Apache-2.0 OR MIT — Details →
48.1.4 16 Aug 2026 none Apache-2.0 OR MIT — Details →
48.1.3 16 Aug 2026 none Apache-2.0 OR MIT — Details →
48.1.2 03 Jul 2026 none Apache-2.0 OR MIT — Details →
48.1.1 29 Jun 2026 none Apache-2.0 OR MIT — Details →
48.1.0 29 Jun 2026 none Apache-2.0 OR MIT — Details →
48.0.13 15 Jun 2026 none Apache-2.0 OR MIT — Details →
48.0.12 12 Jun 2026 none Apache-2.0 OR MIT — Details →
48.0.11 29 May 2026 none Apache-2.0 OR MIT — Details →
48.0.10 29 May 2026 none Apache-2.0 OR MIT — Details →
48.0.9 28 May 2026 none Apache-2.0 OR MIT — Details →
48.0.8 28 May 2026 none Apache-2.0 OR MIT — Details →
48.0.7 28 May 2026 none Apache-2.0 OR MIT — Details →
48.0.6 25 May 2026 none Apache-2.0 OR MIT — Details →
48.0.5 23 May 2026 none Apache-2.0 OR MIT — Details →
48.0.4 08 May 2026 none Apache-2.0 OR MIT — Details →
48.0.3 08 May 2026 none Apache-2.0 OR MIT — Details →
48.0.2 08 May 2026 none Apache-2.0 OR MIT — Details →
48.0.1 04 May 2026 none Apache-2.0 OR MIT — Details →
48.0.0 04 May 2026 none Apache-2.0 OR MIT — Details →
47.2.0 04 May 2026 none Apache-2.0 OR MIT — Details →
47.1.7 21 Apr 2026 none Apache-2.0 OR MIT — Details →
47.1.6 21 Apr 2026 none Apache-2.0 OR MIT — Details →
47.1.5 10 Apr 2026 none Apache-2.0 OR MIT — Details →
47.1.4 10 Apr 2026 none Apache-2.0 OR MIT — Details →
47.1.3 10 Apr 2026 none Apache-2.0 OR MIT — Details →
47.1.2 10 Apr 2026 none Apache-2.0 OR MIT — Details →
47.1.1 10 Apr 2026 none Apache-2.0 OR MIT — Details →
47.1.0 10 Apr 2026 none Apache-2.0 OR MIT — Details →
47.0.26 22 Jan 2026 none Apache-2.0 OR MIT — Details →
47.0.25 07 Dec 2025 none Apache-2.0 OR MIT — Details →
47.0.24 17 Oct 2025 none Apache-2.0 OR MIT — Details →
47.0.23 14 Oct 2025 none Apache-2.0 OR MIT — Details →
47.0.22 17 Sep 2025 none Apache-2.0 OR MIT — Details →
47.0.21 05 Aug 2025 none Apache-2.0 OR MIT — Details →
47.0.20 07 Jul 2025 none Apache-2.0 OR MIT — Details →
47.0.19 26 Jun 2025 none Apache-2.0 OR MIT — Details →
47.0.18 24 Jun 2025 none Apache-2.0 OR MIT — Details →
47.0.17 18 Jun 2025 none Apache-2.0 OR MIT — Details →
47.0.16 26 May 2025 none Apache-2.0 OR MIT — Details →
47.0.15 24 May 2025 none Apache-2.0 OR MIT — Details →
47.0.14 24 May 2025 none Apache-2.0 OR MIT — Details →
47.0.13 23 May 2025 none Apache-2.0 OR MIT — Details →
47.0.12 22 May 2025 none Apache-2.0 OR MIT — Details →
47.0.11 21 May 2025 none Apache-2.0 OR MIT — Details →
47.0.10 21 May 2025 none Apache-2.0 OR MIT — Details →
47.0.9 21 May 2025 none Apache-2.0 OR MIT — Details →
47.0.8 21 May 2025 none Apache-2.0 OR MIT — Details →
47.0.7 20 May 2025 none Apache-2.0 OR MIT — Details →
47.0.6 20 May 2025 none Apache-2.0 OR MIT — Details →
47.0.5 20 May 2025 none Apache-2.0 OR MIT — Details →
47.0.4 20 May 2025 none Apache-2.0 OR MIT — Details →
47.0.3 19 May 2025 none Apache-2.0 OR MIT — Details →
47.0.2 19 May 2025 none Apache-2.0 OR MIT — Details →
47.0.1 19 May 2025 none Apache-2.0 OR MIT — Details →
47.0.0 19 May 2025 none Apache-2.0 OR MIT — Details →
46.0.5 19 May 2025 none Apache-2.0 OR MIT — Details →
46.0.4 19 May 2025 none Apache-2.0 OR MIT — Details →
46.0.3 17 May 2025 none Apache-2.0 OR MIT — Details →
46.0.2 14 May 2025 none Apache-2.0 OR MIT — Details →
46.0.1 12 May 2025 none Apache-2.0 OR MIT — Details →
46.0.0 07 May 2025 none Apache-2.0 OR MIT — Details →
45.2.1 23 Apr 2025 none Apache-2.0 OR MIT — Details →
45.2.0 22 Apr 2025 none Apache-2.0 OR MIT — Details →
45.1.4 19 Mar 2025 none Apache-2.0 OR MIT — Details →
45.1.3 10 Mar 2025 none Apache-2.0 OR MIT — Details →
45.1.2 24 Feb 2025 none Apache-2.0 OR MIT — Details →
45.1.1 24 Feb 2025 none Apache-2.0 OR MIT — Details →
45.1.0 24 Feb 2025 none Apache-2.0 OR MIT — Details →
45.0.10 22 Feb 2025 none Apache-2.0 OR MIT — Details →
45.0.9 20 Jan 2025 none Apache-2.0 OR MIT — Details →
45.0.8 05 Dec 2024 none Apache-2.0 OR MIT — Details →
45.0.7 28 Nov 2024 none Apache-2.0 OR MIT — Details →
45.0.6 28 Nov 2024 none Apache-2.0 OR MIT — Details →
45.0.5 28 Nov 2024 none Apache-2.0 OR MIT — Details →
45.0.4 28 Nov 2024 none Apache-2.0 OR MIT — Details →
45.0.3 28 Nov 2024 none Apache-2.0 OR MIT — Details →
45.0.2 19 Nov 2024 none Apache-2.0 OR MIT — Details →
45.0.1 29 Oct 2024 none Apache-2.0 OR MIT — Details →
45.0.0 28 Oct 2024 none Apache-2.0 OR MIT — Details →
44.1.4 11 Oct 2024 none Apache-2.0 OR MIT — Details →
44.1.3 11 Oct 2024 none Apache-2.0 OR MIT — Details →
44.1.2 28 Sep 2024 none Apache-2.0 OR MIT — Details →
44.1.1 09 Aug 2024 none Apache-2.0 OR MIT — Details →
44.1.0 29 Jul 2024 none Apache-2.0 OR MIT — Details →
44.0.3 29 Jul 2024 none Apache-2.0 OR MIT — Details →
44.0.2 29 Jul 2024 none Apache-2.0 OR MIT — Details →
44.0.1 01 Jul 2024 none Apache-2.0 OR MIT — Details →
44.0.0 21 Jun 2024 none Apache-2.0 OR MIT — Details →
43.0.3 21 Jun 2024 none Apache-2.0 OR MIT — Details →
43.0.2 21 Jun 2024 none Apache-2.0 OR MIT — Details →
43.0.1 30 May 2024 none Apache-2.0 OR MIT — Details →
43.0.0 30 May 2024 none Apache-2.0 OR MIT — Details →
42.2.11 01 May 2024 none Apache-2.0 OR MIT — Details →
42.2.10 01 May 2024 none Apache-2.0 OR MIT — Details →
42.2.9 26 Apr 2024 none Apache-2.0 OR MIT — Details →
42.2.8 25 Apr 2024 none Apache-2.0 OR MIT — Details →
42.2.7 25 Apr 2024 none Apache-2.0 OR MIT — Details →
42.2.6 25 Apr 2024 none Apache-2.0 OR MIT — Details →
42.2.5 27 Feb 2024 none — — Details →
42.2.4 12 Feb 2024 none — — Details →
42.2.3 06 Feb 2024 none — — Details →
42.2.2 17 Jan 2024 none — — Details →
42.2.1 17 Jan 2024 none — — Details →
42.2.0 15 Jan 2024 none — — Details →
42.1.3 12 Jan 2024 none — — Details →
42.1.2 12 Jan 2024 none — — Details →
42.1.1 12 Jan 2024 none — — Details →
42.1.0 08 Jan 2024 none — — Details →
42.0.1 06 Jan 2024 none — — Details →
42.0.0 06 Jan 2024 none — — Details →
41.3.5 30 Dec 2023 none — — Details →
41.3.4 30 Dec 2023 none — — Details →
41.3.3 30 Dec 2023 none — — Details →
41.3.2 20 Dec 2023 none — — Details →
41.3.1 20 Dec 2023 none — — Details →
41.3.0 20 Dec 2023 none — — Details →
41.2.0 12 Dec 2023 none — — Details →
41.1.14 03 Dec 2023 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for aegir

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-11059: Sensitive Information Exposure in AEgir 9.6 critical 21.10.1 27 May 2020
CVE-2017-16225: Github Token Leak in aegir N/A high 12.0.8 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 aegir

Is aegir safe to use?

Vulert records 2 vulnerabilities for aegir in npm: 1 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 aegir's Vulert package health score?

Vulert scores aegir 69/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 aegir affected?

No. 48.1.6, 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 aegir should I use?

48.1.6 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 aegir have?

2 vulnerabilities are recorded for aegir in the npm ecosystem: 1 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 aegir vulnerabilities disclosed?

0 vulnerabilities were recorded for aegir 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 aegir 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 aegir for upcoming vulnerabilities?

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