VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

angular-expressions: vulnerability history, versions and safety

angular-expressions is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 26 releases, from Jan 2020 to May 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 C2 H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 11 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all angular-expressions vulnerabilities

Vulert verdict on angular-expressions 1.7.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 1.7.1 — unaffected i
  • Vulnerabilities on record 4 over 6 years · 1 in the last year i
  • Latest disclosure 11 May 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 0 i
  • Depended on by 59 packages i
  • Stars 100 i
  • OpenSSF scorecard 2/10 i
  • Last release this month i
  • Licence Unlicense 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 angular-expressions, 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.7.1 12 Oct 2026 none Unlicense — Details →
1.7.0 21 Sep 2026 none Unlicense — Details →
1.6.0 30 Jul 2026 none Unlicense — Details →
1.5.5 18 May 2026 none Unlicense — Details →
1.5.4 13 May 2026 none Unlicense — Details →
1.5.3 11 May 2026 none Unlicense — Details →
1.5.2 07 May 2026 none Unlicense — Details →
1.5.1 12 Aug 2025 C1 Unlicense Yes Details →
1.5.0 03 Jul 2025 C1 Unlicense Yes Details →
1.4.3 10 Dec 2024 C1 Unlicense Yes Details →
1.4.2 25 Nov 2024 C2 Unlicense Yes Details →
1.4.1 25 Nov 2024 C2 Unlicense Yes Details →
1.4.0 17 Oct 2024 C2 Unlicense Yes Details →
1.3.0 24 Sep 2024 C2 Unlicense Yes Details →
1.2.1 24 Jan 2024 C2 Unlicense Yes Details →
1.2.0 12 Jan 2024 C2 Unlicense Yes Details →
1.1.10 04 Jan 2024 C2 Unlicense Yes Details →
1.1.9 20 May 2023 C2 Unlicense Yes Details →
1.1.8 20 Oct 2022 C2 Unlicense Yes Details →
1.1.7 19 Oct 2022 C2 Unlicense Yes Details →
1.1.6 19 Oct 2022 C2 Unlicense Yes Details →
1.1.5 18 Feb 2022 C2 Unlicense Yes Details →
1.1.4 27 Aug 2021 C2 Unlicense Yes Details →
1.1.3 12 Feb 2021 C2 Unlicense Yes Details →
1.1.2 29 Jan 2021 C2 Unlicense Yes Details →
1.1.1 15 Mar 2020 C2 H1 Unlicense Yes Details →
1.1.0 05 Mar 2020 C2 H1 Unlicense Yes Details →
1.0.1 23 Jan 2020 C2 H1 Unlicense Yes Details →
1.0.0 06 Oct 2018 C2 H2 Unlicense Yes Details →
0.3.0 16 Sep 2015 C2 H2 Unlicense Yes Details →
0.2.1 09 Apr 2014 C2 H2 Unlicense Yes Details →
0.2.0 09 Apr 2014 C2 H2 Unlicense Yes Details →
0.1.0 16 Mar 2014 C2 H2 Unlicense Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1
  • 2024 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 angular-expressions

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-54152: Angular Expressions Remote Code Execution Vulnerability 9.3 critical 1.4.3 10 Dec 2024
CVE-2026-44643: Angular Expressions Remote Code Execution Vulnerability 9.3 critical 1.5.2 11 May 2026
CVE-2021-21277: Angular Expressions - Remote Code Execution 8.8 high 1.1.2 01 Feb 2021
CVE-2020-5219: Remote Code Execution in Angular Expressions 8.7 high 1.0.1 24 Jan 2020

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 angular-expressions

Is angular-expressions safe to use?

Vulert records 4 vulnerabilities for angular-expressions in npm: 2 critical, 2 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 angular-expressions's Vulert package health score?

Vulert scores angular-expressions 66/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 angular-expressions affected?

No. 1.7.1, 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.

How many vulnerabilities does angular-expressions have?

4 vulnerabilities are recorded for angular-expressions in the npm ecosystem: 2 critical, 2 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 angular-expressions vulnerabilities disclosed?

1 vulnerability was recorded for angular-expressions in the last 12 months, and the oldest entry in this database dates to 24 Jan 2020. 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 angular-expressions 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 angular-expressions for upcoming vulnerabilities?

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