VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@openclaw/msteams: vulnerability history, versions and safety

@openclaw/msteams is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 89 releases, first recorded in Oct 2026. 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 M1
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 05 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @openclaw/msteams vulnerabilities

Vulert verdict on @openclaw/msteams 2026.10.6 i

Updated on 23 Oct 2026

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

Package health score 96/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

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

  • Current release 2026.10.6 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 05 Oct 2026 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Stars 392,192 i
  • Last release this month 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 @openclaw/msteams, 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
2026.10.6 22 Oct 2026 none — — Details →
2026.10.10-beta.3 21 Oct 2026 none — — Details →
2026.10.5 18 Oct 2026 none — — Details →
2026.10.10-beta.2 17 Oct 2026 none — — Details →
2026.10.4 15 Oct 2026 none — — Details →
2026.10.10-beta.1 15 Oct 2026 none — — Details →
2026.9.33 15 Oct 2026 none — — Details →
2026.10.5-beta.4 15 Oct 2026 none — — Details →
2026.10.3 13 Oct 2026 none — — Details →
2026.10.5-beta.3 13 Oct 2026 none — — Details →
2026.10.5-beta.2 12 Oct 2026 none — — Details →
2026.10.2 12 Oct 2026 none — — Details →
2026.10.5-beta.1 11 Oct 2026 none — — Details →
2026.10.1 10 Oct 2026 none — — Details →
2026.9.9 08 Oct 2026 none — — Details →
2026.10.1-beta.2 07 Oct 2026 none — — Details →
2026.10.1-beta.1 05 Oct 2026 none — — Details →
2026.9.8 03 Oct 2026 none — — Details →
2026.8.35 02 Oct 2026 none — — Details →
2026.8.34 01 Oct 2026 none — — Details →
2026.9.7 30 Sep 2026 none — — Details →
2026.8.33 27 Sep 2026 none — — Details →
2026.9.6 23 Sep 2026 none — — Details →
2026.7.35 21 Sep 2026 M1 — Yes Details →
2026.7.34 20 Sep 2026 M1 — Yes Details →
2026.9.5 18 Sep 2026 none — — Details →
2026.7.33 18 Sep 2026 M1 — Yes Details →
2026.9.4 11 Sep 2026 none — — Details →
2026.6.35 10 Sep 2026 M1 — Yes Details →
2026.9.3 08 Sep 2026 none — — Details →
2026.9.2 05 Sep 2026 none — — Details →
2026.9.1 03 Sep 2026 none — — Details →
2026.8.2 01 Sep 2026 none — — Details →
2026.8.1 31 Aug 2026 none — — Details →
2026.9.1-beta.1 28 Aug 2026 none — — Details →
2026.8.1-beta.3 24 Aug 2026 M1 — Yes Details →
2026.8.1-beta.2 15 Aug 2026 M1 — Yes Details →
2026.6.34 04 Aug 2026 M1 — Yes Details →
2026.7.2-beta.7 02 Aug 2026 M1 — Yes Details →
2026.7.2-beta.5 28 Jul 2026 M1 — Yes Details →
2026.7.2-beta.4 24 Jul 2026 M1 — Yes Details →
2026.6.33 21 Jul 2026 M1 — Yes Details →
2026.7.2-beta.3 18 Jul 2026 M1 — Yes Details →
2026.7.2-beta.2 17 Jul 2026 M1 — Yes Details →
2026.7.2-beta.1 15 Jul 2026 M1 — Yes Details →
2026.7.1 13 Jul 2026 M1 — Yes Details →
2026.7.1-beta.6 13 Jul 2026 M1 — Yes Details →
2026.7.1-beta.5 11 Jul 2026 M1 — Yes Details →
2026.7.1-beta.4 11 Jul 2026 M1 — Yes Details →
2026.7.1-beta.2 05 Jul 2026 M1 — Yes Details →
2026.7.1-beta.1 02 Jul 2026 M1 — Yes Details →
2026.6.11 30 Jun 2026 M1 — Yes Details →
2026.6.11-beta.2 28 Jun 2026 M1 — Yes Details →
2026.6.10 24 Jun 2026 M1 — Yes Details →
2026.6.10-beta.2 22 Jun 2026 M1 — Yes Details →
2026.6.10-beta.1 21 Jun 2026 M1 — Yes Details →
2026.6.9 21 Jun 2026 M1 — Yes Details →
2026.6.9-beta.1 19 Jun 2026 M1 — Yes Details →
2026.6.8 16 Jun 2026 M1 — Yes Details →
2026.6.8-beta.2 16 Jun 2026 M1 — Yes Details →
2026.6.8-beta.1 14 Jun 2026 M1 — Yes Details →
2026.6.6 12 Jun 2026 M1 — Yes Details →
2026.6.6-beta.2 12 Jun 2026 M1 — Yes Details →
2026.6.6-beta.1 11 Jun 2026 M1 — Yes Details →
2026.6.5 09 Jun 2026 M1 — Yes Details →
2026.6.5-beta.6 09 Jun 2026 M1 — Yes Details →
2026.6.5-beta.5 08 Jun 2026 M1 — Yes Details →
2026.6.5-beta.3 08 Jun 2026 M1 — Yes Details →
2026.6.5-beta.2 07 Jun 2026 M1 — Yes Details →
2026.6.5-beta.1 06 Jun 2026 M1 — Yes Details →
2026.6.2-beta.1 03 Jun 2026 M1 — Yes Details →
2026.6.1 03 Jun 2026 M1 — Yes Details →
2026.6.1-beta.3 03 Jun 2026 M1 — Yes Details →
2026.6.1-beta.2 02 Jun 2026 M1 — Yes Details →
2026.6.1-beta.1 01 Jun 2026 M1 — Yes Details →
2026.5.31-beta.4 01 Jun 2026 M1 — Yes Details →
2026.5.31-beta.3 31 May 2026 M1 — Yes Details →
2026.5.31-beta.2 31 May 2026 M1 — Yes Details →
2026.5.31-beta.1 31 May 2026 M1 — Yes Details →
2026.5.30-beta.1 31 May 2026 M1 — Yes Details →
2026.5.28 30 May 2026 M1 — Yes Details →
2026.5.28-beta.4 29 May 2026 M1 — Yes Details →
2026.5.28-beta.3 29 May 2026 M1 — Yes Details →
2026.5.28-beta.2 29 May 2026 M1 — Yes Details →
2026.5.28-beta.1 29 May 2026 M1 — Yes Details →
2026.5.27 28 May 2026 M1 — Yes Details →
2026.5.27-beta.1 28 May 2026 M1 — Yes Details →
2026.5.26 27 May 2026 M1 — Yes Details →
2026.5.26-beta.2 27 May 2026 M1 — Yes Details →
2026.5.26-beta.1 26 May 2026 M1 — Yes Details →
2026.5.25-beta.1 26 May 2026 M1 — Yes Details →
2026.5.24-beta.2 25 May 2026 M1 — Yes Details →
2026.5.24-beta.1 24 May 2026 M1 — Yes Details →
2026.5.22 24 May 2026 M1 — Yes Details →
2026.5.20 21 May 2026 M1 — Yes Details →
2026.5.20-beta.2 21 May 2026 M1 — Yes Details →
2026.5.20-beta.1 21 May 2026 M1 — Yes Details →
2026.5.19 20 May 2026 M1 — Yes Details →
2026.5.19-beta.2 20 May 2026 M1 — Yes Details →
2026.5.19-alpha.1 20 May 2026 M1 — Yes Details →
2026.5.18 18 May 2026 M1 — Yes Details →
2026.5.18-beta.1 18 May 2026 M1 — Yes Details →
2026.5.16-beta.7 18 May 2026 M1 — Yes Details →
2026.5.16-beta.6 18 May 2026 M1 — Yes Details →
2026.5.16-beta.5 17 May 2026 M1 — Yes Details →
2026.5.16-beta.4 17 May 2026 M1 — Yes Details →
2026.5.16-beta.3 16 May 2026 M1 — Yes Details →
2026.5.16-beta.2 16 May 2026 M1 — Yes Details →
2026.5.16-beta.1 16 May 2026 M1 — Yes Details →
2026.5.14-beta.2 15 May 2026 M1 — Yes Details →
2026.5.14-beta.1 14 May 2026 M1 — Yes Details →
2026.5.12 14 May 2026 M1 — Yes Details →
2026.5.12-beta.8 14 May 2026 M1 — Yes Details →
2026.5.12-beta.7 14 May 2026 M1 — Yes Details →
2026.5.12-beta.6 13 May 2026 M1 — Yes Details →
2026.5.12-beta.5 13 May 2026 M1 — Yes Details →
2026.5.12-beta.4 13 May 2026 M1 — Yes Details →
2026.5.12-beta.3 12 May 2026 M1 — Yes Details →
2026.5.12-beta.2 12 May 2026 M1 — Yes Details →
2026.5.12-beta.1 12 May 2026 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for @openclaw/msteams

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-100582: OpenClaw Package Vulnerability in Channel Read Actions 6.5 medium 2026.8.1 05 Oct 2026

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 @openclaw/msteams

Is @openclaw/msteams safe to use?

Vulert records 1 vulnerabilities for @openclaw/msteams in npm: 0 critical, 0 high, 1 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 @openclaw/msteams's Vulert package health score?

Vulert scores @openclaw/msteams 96/100, which reads as healthy. 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 @openclaw/msteams affected?

No. 2026.10.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.

How many vulnerabilities does @openclaw/msteams have?

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

1 vulnerability was recorded for @openclaw/msteams in the last 12 months, and the oldest entry in this database dates to 05 Oct 2026. 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 @openclaw/msteams 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 @openclaw/msteams for upcoming vulnerabilities?

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